Skip to main content

Webhook History & Troubleshooting

CloudFFL receives webhook notifications from FastBound whenever certain events occur — most importantly when a Form 4473 is completed. The Webhook History view lets you see every incoming webhook event, its status, and troubleshoot any issues.

Where to Find It

Go to FastBound → Configuration → Webhook History. This view requires the FastBound / Manager security role or higher.

What the List Shows

Each row in the Webhook History list represents one incoming event from FastBound. The columns include:

  • Date — When the webhook was received
  • Event Type — The type of FastBound event (e.g., form4473.completed)
  • Status — Whether the webhook was processed successfully or failed
  • FastBound Account — Which FastBound configuration received the event
  • Related Record — The Sales Order or other record that was updated by this webhook

Understanding Webhook Statuses

Status What It Means
Success The webhook was received and processed. The related record was updated.
Failed The webhook was received but something went wrong during processing. Check the error details on the record.
Received The webhook arrived but has not yet been fully processed.

Troubleshooting Common Issues

No webhooks appearing

  • Verify that webhooks are set up: go to FastBound → Configuration → FastBound Accounts, open your account, and check that you have clicked Setup Webhooks.
  • Confirm that your CloudFFL instance is reachable from the internet (FastBound needs to send HTTP requests to your server).
  • Check that the webhook URL in FastBound's settings matches your CloudFFL domain.

Webhook shows "Failed" status

  • Open the webhook history record to see the error message and payload details.
  • Common causes: the related Sales Order was deleted or archived, the FastBound account was deactivated, or there was a temporary server error.
  • If the error is transient, you may be able to reprocess by correcting the underlying issue and waiting for the next webhook from FastBound.

4473 completed in FastBound but Sales Order not updated

  • Check Webhook History for a matching form4473.completed event.
  • If no event exists, the webhook may not have fired from FastBound — verify webhook configuration on both sides.
  • If the event exists but failed, check the error details for the specific cause.
  • As a workaround, you can manually update the Sales Order's 4473 Completed flag and enter the NTN number.
Tip: Webhook History is a diagnostic tool. Under normal operation, you should not need to check it regularly. It is most useful when a 4473 completion does not appear to have synced back to CloudFFL.
Back to top