Feature
See what a workflow ran, and where it stopped
Every production run is tied to the deployed version. Open the run to see the steps, including a step that failed or a step that is waiting for approval.
What is recorded
The run stores its status and its steps. A queued run can be cancelled before it starts. A run that is already going can be stopped. Finished runs stay on the version they started with, even if you later deploy a different version.
Example
A Gmail crew fails on the send because the Google connection expired. The run shows that step as failed. You reconnect Gmail and test the latest version. The failed run is not silently replayed.
Limits
There is no automatic retry of a failed step in the executor. Monitoring here means you can see the run and decide whether to test again or deploy a fix. CrewX24 does not publish an uptime percentage.
Questions
Will a failed step retry on its own?
No. Look at the run, fix the connection or the workflow, and test or run it again yourself.
Can I tell which version ran?
Yes. A run is pinned to the version that was current when it started. Deploying a newer version does not rewrite that run.