Use Live Trail to review a scenario run
Live Trail shows a scenario run as it happens. It combines module requests and run activity in one chronological list, so you can follow a run in the scenario editor and see what went wrong without leaving the canvas.
Access requirements
| table 0-row-2 1-row-2 2-row-2 layout-auto html-authored no-header | |
|---|---|
| Adobe Workfront package |
Any Adobe Workfront Workflow package and any Adobe Workfront Automation and Integration package Workfront Ultimate Workfront Prime and Select packages, with an additional purchase of Workfront Fusion. |
| Adobe Workfront licenses |
Standard Work or higher |
| Product | If your organization has a Select or Prime Workfront package that does not include Workfront Automation and Integration, your organization must purchase Adobe Workfront Fusion. |
For more detail about the information in this table, see Access requirements in documentation.
Open Live Trail
- Click the Scenarios tab in the left panel.
- Select the scenario that you want to review.
- Click anywhere on the scenario to enter the Scenario editor.
- Start a run of the scenario, for example by clicking Run once.
Live Trail opens in the panel on the right side of the canvas. If you close the panel during a run, a small tab on the right of the screen lets you open it again without losing the events that were captured.
Review events in Live Trail
Live Trail lists module requests and run activity in the order that they happen. You can:
- Search the list.
- Filter the list by status.
- Follow the newest event as the run continues.
- Clear the current trail.
View request and response details
-
In Live Trail, click the request that you want to view details for.
The module that made the request is revealed on the canvas, and the request and response details open in the panel.
-
Review the details. The detail view includes:
- Navigation between the operations of the module
- Request headers and body
- Response headers and body
-
(Optional) Copy the details to use them elsewhere by clicking Copy raw or Copy cURL:
- Copy a raw report of the request and response.
- Copy a cURL command for the request.
-
To return to the list, click the back arrow at the upper-left of the panel.
Make sure request and response details are available
Request and response details are not kept for every scheduled or triggered run, because they take a lot of storage.
- Run once always keeps request and response details.
- For a scenario’s regular runs, turn on Temporary debug logs in the scenario settings before the runs that you want to inspect. For more information, see Temporary debug logs in the article Configure scenario settings.
If you open a run from the execution history and the request and response panel has no data, the panel directs you to the Temporary debug logs setting.