Troubleshoot your integration
Resolve access, request, mailbox and delivery errors using settings and delivery logs.
By HaulMatch · Updated
Integrations are in preview. Setup access depends on rollout and provider configuration. If your settings show integrations are not enabled, contact HaulMatch for availability. Contact us.
On this page
Integrations are not enabled
The release is in preview and requires rollout and provider configuration. If the settings explicitly say Organization integrations are not enabled, contact HaulMatch for access. You can still read the setup guides and prepare your mappings.
A temporary service outage is a different condition. Retain your request IDs and retry when service returns; do not create new identities for an uncertain write.
API error codes
| HTTP status | What to check |
|---|---|
| 400 | Check required fields, enum values, dates, units and payload shape in the OpenAPI reference. |
| 401 | Use an active organization integration key in the Bearer header, rather than a portal session token. |
| 403 | Check scopes, current membership, organization, team assignment and job lifecycle permissions. |
| 404 | Check the resource ID and whether it belongs to the authorized organization. |
| 409 | Inspect the original idempotency key, payload, external reference and lifecycle state before retrying. |
| 503 | Check whether integrations or the required provider are available. Preserve request identity when retrying. |
Missing settings or team access
Connections, Email and Company wallet require the Owner role. Fleet configuration also requires a carrier organization. Submanagers can only work with their assigned teams. Ask the organization owner to check membership and team assignments.
Credentials and connected mailboxes are disabled when their owner loses the required membership. The owner must create or reconnect an authorized replacement.
Mailbox messages or drafts are missing
- Send a new message after connection or folder selection; previous history is deliberately skipped.
- Allow for the two-minute poll interval and check the chosen folder, connection status and last error.
- For forwarding, use the generated intake address and check the exact sender allowlist.
- Check attachment types, ten-file and 10 MB limits, and exact CSV headers. Review extraction warnings or enter missing fields manually.
- If the provider cursor expires, HaulMatch starts a fresh baseline and shows a warning. Reconnect or send a new request after fixing access.
Webhook delivery fails
Check the delivery log for timeout, response or destination errors. Your receiver must use public HTTPS on port 443, respond without redirects, and verify the original raw body. Ensure the active secret matches the configured subscription.
Fix the receiver and replay the delivery using authorized settings. Deduplicate by event ID so retries do not create duplicate work.
An outgoing email is uncertain
ACCEPTED means the provider accepted the send; Resend receipts can later report DELIVERED or FAILED. Gmail and Outlook delivery receipts are not tracked.
UNKNOWN means a connected mailbox send had an uncertain outcome. Check Sent mail before replaying and explicitly confirm any repeat send. An ordinary definitive delivery failure does not automatically mean UNKNOWN.
Company payment or dispatch is blocked
For COMPANY pay, check reviewed company verification, GST evidence and Stripe transfer/payout readiness. Before transit, check the assigned member driver, team, driver verification and held payment.
Company funding, release and withdrawals require the signed-in owner. Inspect existing payment and payout status before retrying. Changing the operating driver does not change the commercial payee.
Contact support
Share the organization ID, relevant job or quote ID, request or event ID, approximate time and the error message. Keep API keys, webhook secrets, mailbox tokens and personal documents out of your support message.