Execution history walkthrough

Review the execution history for the “Using the mighty filter” scenario to understand what happened when executions occurred and how they were structured when they were run.

An image of execution history in a Fusion scenario

Execution history walkthrough

Workfront recommends watching the exercise walkthrough video before trying to recreate the exercise in your own environment.

The purpose of this walkthrough exercise is to introduce you to the execution history for a scenario. The execution history gives you a great overview of what operations were run successfully or not within your scenario, and it gives you visibility into what your scenario looked like at that point in time. To prepare for this walkthrough exercise, we’ll navigate back to our third walkthrough that we created using the Mighty Filter.
Let’s start by returning to the third walkthrough exercise we created called Using the Mighty Filter. As you build more and more scenarios in your system, it’s going to be harder to navigate and find them in the list of available scenarios. Luckily at the top left hand corner of the Scenario section we can search for keywords in our scenario titles. In this case, I could type in the word filter and find the scenario that we’re looking for. Let’s go into Using the Mighty Filter.
I’m brought to the scenario overview page and I’m going to click at the top into the History tab.
Here I can see the overall history for my scenario. Whether I edited the scenario or I had successful runs of the scenario, I can view this information here. There’s two ways I can filter as I build out a bigger execution history. I can choose to filter by the start date and put brackets around the started and the ended timeframes or I can choose to filter by the status. Success, warning, or error will be covered in future courses.
Let’s dig a little bit deeper into our first successful execution by clicking on the Details button at the far right.
In the next screen that appears, I can see in the top right hand corner the Run ID for this specific execution, the duration time, the operations that were run, and the size of the execution.
Below that, I have a simple log which will show me which operations were successful or not for this specific execution.
Hovering over an item in the list will show me where in my scenario an operation was successful or not.
Clicking on one of those items will open the Execution Inspector and show me what bundle was processed.
Below each item in the list I have a short descriptive sentence telling me whether the operation was completed or potentially the bundle did not pass through the filter. If I click over to the advanced log, I essentially get the same information with a little bit more around when the module was initialized or when the scenario was initialized. And at the bottom I can see when the module was finalized and when the scenario was finalized.
The panel at the left is really amazing because it shows me exactly what my scenario was designed like when this execution was run. I also have the Execution Inspector which will show me which bundles of information passed through at this specific time. -

Fulltext search in the history tab

Fulltext search is available in the history tab of a scenario, allowing you to search for any data processed in the scenario.

An image of execution history search

Instead of opening each execution to search for data, Fulltext search searches across all executions within a single scenario. The search results provide a list of executions where the data was found, and you can click any execution to explore further.

An image of an execution history search

The search results contain some useful icons in the image below.

A—The status of the execution.

B—Whether the data was in the input or the output of the module in which it was found.

C—The execution ID.

D—Copy the execution ID.

An image of an execution history search results

When you click on an execution, Workfront Fusion loads the execution and the module where the search result was found. And it opens the execution inspector on the module that contains the search data.

An image of an execution history links

Want to learn more? We recommend the following:

Workfront Fusion documentation