Where did that run come from? Debugging just got faster
We have improved the Source Run column in the scenario execution history.
Instead of just showing the execution ID, the source run now provides a more meaningful context.
What’s new:
-
Original runs linked: The source run column now displays a direct link to the original run, so you never lose the thread. -
Timestamps for replays: If it’s a re-run, you’ll see the timestamp of the original run immediately. -
Parent visibility: Triggered by another scenario? We now display the parent scenario’s name right in the list (trimmed when too long).
Feature walkthrough video
Why is this useful?
-
Debug at a glance: Stop opening individual logs just to trace origin. See immediately whether a run originated from a parent scenario or a manual trigger, without leaving the history table.
-
Trace complex lineages: For those of you building nested architectures, you can now instantly verify which “Parent” kicked off the “Child” process. No more guessing games.
-
Cleaner troubleshooting: Distinguish replays from fresh runs instantly. The original timestamp persists, giving you the exact context you need to fix issues faster
Hope you find this update useful as well!
Happy automating 
Valery