Troubleshoot connector delivery
Resolve validation, authentication, destination, and delivery-state problems.
Diagnose connector validation, authentication, destination, and delivery-state problems without exposing secrets or resending blindly.
Why it matters
The saved revision, visible state, bounded HTTP detail, and Delivery ID narrow the problem to configuration, a temporary destination condition, or an eligible terminal failure. This keeps recovery deliberate and preserves the original evidence.
Where to work
Open Company -> Connectors, select Edit for the connector, and compare its Saved revision with Delivery history. Use the editor for configuration changes and the eligible history row for Resend.
Steps
- Identify the affected connector, lead, Delivery ID, timestamp, saved revision, visible state, and HTTP status or bounded message.
- If the form will not save, resolve every field error before testing again.
- If Test draft and real delivery differ, confirm that the intended values were saved, the connector was active, and the lead was accepted after activation.
- If authentication or a provider-owned field failed, replace the credential or correct the exact destination identifier, then Test draft and Save changes.
- If delivery is still automatic, wait and refresh rather than editing, reactivating, or resending.
- If a failed attempt offers Resend, review the current connector configuration and current lead data, enter the required reason, and acknowledge the duplicate risk.
- Track the new Delivery ID separately and verify the destination without changing the original attempt.
Choose recovery from the visible state
The form will not save
Read every field error. If the payload or a custom header references unsupported or unselected placeholders, select the complete required set or remove those references.
Do not broaden Successful HTTP statuses or remove validation simply to make an invalid draft save.
Test draft succeeds but real delivery does not
Test draft uses the values currently visible in the editor. Real delivery uses the last saved active revision.
Confirm that Save changes completed, the connector was activated or resumed, and the affected lead was accepted after that state became active.
Authentication failed
Create or rotate the credential in the provider, enter the complete replacement under Replace credential, run a synthetic test, and save the reviewed revision.
The masked suffix can identify a normal-length saved credential but cannot recover it. Never send the complete replacement in support evidence.
The provider rejected a field
Compare the payload with provider-owned identifiers: HubSpot internal property names, Pipedrive custom Person field keys, HighLevel location IDs, Salesforce form fields, or the receiver's own JSON contract.
Correct the exact identifier and keep Payload fields synchronized with every HoneyFalcon placeholder.
The HTTP response is not considered successful
Compare the visible HTTP status with the shipped preset and the provider's documented acceptance contract. Add a status only when the destination legitimately uses it for an accepted request.
Do not allow a broad status range to hide authentication, validation, or server failures.
Automatic delivery is still in progress
Queued, in-flight, and retryable attempts continue through the automatic delivery path. Refresh after a short interval.
Do not repeatedly edit or reactivate the connector while diagnosing the original attempt, and do not create a competing manual resend.
Resend is available
Resend is shown only for an eligible failed attempt. It uses the current connector configuration and current lead data, requires a reason, and creates a new Delivery ID.
The destination may receive duplicate data. Confirm that risk before continuing, track the new result separately, and leave the original attempt unchanged.
The destination is blocked
Use the provider's public HTTPS endpoint. HoneyFalcon rejects unsafe local, private, link-local, embedded-credential, prohibited DNS, and prohibited redirect targets.
Resolve the endpoint contract instead of bypassing the safety check.
Collect bounded support evidence
Share the page, connector name, Lead ID, Delivery ID, saved revision, timestamp, visible state, HTTP status, and exact non-secret message shown by HoneyFalcon.
Do not share the credential, Authorization header, full payload, secret destination URL, or unmasked personal data.
Resend only an eligible terminal failure after reviewing duplicate risk. It uses current connector configuration and current lead data, creates a new Delivery ID, and never rewrites the original attempt.
Troubleshooting is complete when
- The visible state and saved revision identify the smallest appropriate corrective action.
- Any credential or mapping fix is tested with synthetic data and saved as a reviewed revision.
- Automatic delivery is allowed to finish, or an eligible Resend produces a separately tracked Delivery ID.
- The destination result is verified with bounded evidence and no secret or unnecessary personal data is exposed.