Skip to main content
Workflow execution logs show how individual workflows are processed for each user and show step-by-step workflow execution details. You can see how each node in the workflow is executed. All the errors that happen during workflow execution are logged here, except delivery errors since they are reported later by vendor and is tracked in Message Logs.
Each workflow execution log entry includes these sections:
  • Overview: Generic information about the workflow execution:
    • Workflow slug, tenant ID and Recipient (clickable)
    • Execution ID (share this with SuprSend support if you need help in debugging the workflow or want to report an issue)
    • Idempotency key (unique identifier of the request passed to SuprSend)
    • Status (Completed, Partial Failure, Failed)
    • Start time (workflow start timestamp)
    • Preference category
  • Workflow diagram: Visual path of the execution and color coded status against each node. Check the failed nodes for error details.
  • Execution history: Chronological logs of workflow start, node execution, channel computation, template rendering, and notification triggers.
Status indicators: Common errors captured:
Any error that can be evaluated within SuprSend are logged here, except for delivery errors which are tracked in Message Logs. Navigate from here: If your workflow execution has delivery or webhook nodes, their corresponding logs are available in Message logs. Click on view message logs in delivery nodes to navigate to the corresponding message log.
“Completed” execution does not mean “Delivered”. A workflow can complete successfully but still have message delivery failures. Check Message logs for actual delivery status.