Invocation History

Inspect past scenario runs to troubleshoot issues and confirm expected behavior.

Invocation history shows every top-level scenario execution with timestamps, statuses, and payload details. Use it to trace data through your flow, debug failures, and prove that automations ran when expected. Scenarios invoked from other scenarios are embedded inside the caller and do not appear as separate entries.

What you’ll find

• Run status, duration, and trigger source (manual, scheduled, webhook, or chained call).
• Input payloads and mapped variables at each step.
• Outputs returned to callers or downstream systems.
• Errors, retries, and any logged messages from steps that expose diagnostics.

Typical workflows

• Validate a new scenario by comparing sample inputs to outputs before going live.
• Investigate a failed order sync by drilling into the exact step and payload that errored.
• Confirm SLAs by filtering runs within a timeframe and checking duration trends.
• Export or reference run IDs when discussing incidents with your team.

Next steps

• Pair history with alerts so you’re notified on repeated failures.
• Keep sample payloads handy for common issues to speed up replays and fixes.