Action History Tracking (Workflow Executions)
The robust technical ledger strictly logging the real-time statuses (successful, failed, pending) of previously fired workflows along with step-by-step raw data operations. Maintain absolute transparency over your automations.
What are Workflow Executions?
No matter how exceptionally brilliant a designed pipeline (Workflow) seems, absolute runtime errors originating from server bottlenecks, invalid user inputs, or foreign API services might unavoidably arise during its actual operation. The "Executions" screen is the granular system log panel where we chronologically inspect the heartbeat of the platform. You can natively check whether the active pipeline genuinely completed without errors (Success) or crashed midway (Failed) throughout the day.
🔍 Live Status Auditing
Entering the list, administrators observe the split-second realities of individual operational lifecycles. Easily sort thousands of logs by their absolute statuses such as Queued, Running, Completed, or Failed to instantly detect any operational anomaly.
🐛 Step-by-Step Debugging
When clicking on a failed transaction record (Execution ID), the screen doesn't just display a generic error. It visually highlights on exactly which "Node" the algorithm critically broke and what exactly that error output was (e.g., HTTP 504 Timeout fault or Invalid JSON Payload).
📦 Raw Payload Inspection
Every automated pipeline functions akin to a closed "black box". The "Executions" module forcefully opens that box. You can natively click on any completed Node on the timeline and see the exact raw JSON data that was inputted and outputted during that specific microsecond.
Developer Usecase: Resolving Silent Failures
A marketing automation workflow is supposed to push new user emails to Mailchimp. Users complain they aren't receiving newsletters. Without this logging architecture, a developer would spend days adding custom code just to find the issue. With the Executions Panel, the developer simply filters by "Failed" workflows from today, clicks the exact Mailchimp Node that turned red, and instantly reads the API response: "API Key Expired". The issue is pinpointed and fundamentally resolved within 30 seconds.
Comments
Leave a comment