Fluent Commerce Logo
Docs

Basic Knowledge

Essential Knowledge articles related to the Workflow Framework (Rubix)

Webhook Retries and Inline Events

Essential knowledgeCore knowledge to understand Fluent Commerce
This page explains how the Orchestration Engine retries a webhook that is reached through inline events, and helps you decide which value of `fc.rubix.webhook.retry.event` to use for your account.It describes how each workflow pattern is affected, what each value does, and what to check before you change the setting.
  • Prerequisites: Webhooks, Inline Event, Understanding Event Execution
  • A webhook action is retried only when its request fails with a network error, such as a timeout. This happens most often when the receiving system is under load, for example during peak trading
  • With `webhook-event`, the retry uses the webhook event, which is the event that triggered the ruleset in which the webhook action was produced:
    • The retry is posted to the same endpoint with the same event as the original call
    • If the receiving system responds, with any HTTP status code, the retry counts as delivered and retries stop
    • If all retries fail, the Exception event is raised for the ruleset and entity of the webhook event
  • With `initial-event`, the retry uses the initial event, which is the event that started the event context:
    • The retry is posted to the same endpoint, but with the initial event, so the event name, the entity, and the attributes can differ from the original call
    • If the receiving system responds, with any HTTP status code, the retry counts as delivered and retries stop. The original call isn’t sent again, and the Send Webhook audit event shows `SUCCESS`, so the failure goes unnoticed
    • If all retries fail, the Exception event is raised for the ruleset and entity of the initial event, not for the ruleset of the webhook event
  • The values differ only when the webhook event is an inline event. When the webhook action is produced in the ruleset triggered by the initial event, both values give the same retry
  • Accounts created before the setting was introduced keep `initial-event` until you change it. Accounts created since then use `webhook-event`. Check your workflows with this page, then switch to `webhook-event`
  • For custom webhook rules and the reference `SendWebhook` rule, also add `preserve-event-details` to the workflow, so the retry reruns the rule that produced the webhook action. Without it, the retry is sent by the built-in platform webhook rule. See `fc.rubix.sdk.webhook.retry.method`.