Incomplete executions walkthrough

The purpose of this walkthrough exercise is to demonstrate the immense value that storing incomplete executions provides. Here we’ll clone our creating different paths using routers scenario and we’ll create some intentional errors that now give us the opportunity to resolve because we’re storing that incomplete execution. To be successful in this walkthrough exercise, you’ll want to clone this scenario from our previous walkthrough, and you’ll want to have your test drive pulled up to the Shipping Manifest Project from the first part of the training.

Let’s start by returning to our creating different paths using routers, error handling test scenario. If you didn’t save the intentional errors we created from the error handling course previously, that’s okay. We’re going to create a new one this time. To start, I’m going to go down to my control panel and click on Scenario settings.

And here I’m going to select Allow storing of incomplete executions. Clicking OK, I’ll then go into my Create a task for each character module. I’ll find the project ID that we had mapped over previously from our Workfront system and I’ll delete it.

And this will intentionally create an error because a task cannot exist within Workfront without belonging to a project. So we’ll click Save, and we’ll run our scenario.

Once our scenario finishes running, we’ll now notice that we have a warning symbol on our Create a task for each character module.

Here you’ll see a difference in the error that we see in the module panel. We now have a Resolve button. In the next video, we’ll show you how you can go to the incomplete execution history section and resolve these errors.

Picking up where we left off, you can see in the module panel that we have a bundle of information that tried to pass through this module but resulted in an error. I can click the Resolve button, which will take me to the Incomplete Executions section for this specific record. At first glance, it doesn’t appear that much is going on in the section, but if you click into where your scenario is located in the center of the screen, it will now bring you into the area that looks like the scenario designer but is actually where you’re just going to resolve the incomplete execution for that specific bundle.

Consider this a blueprint of the scenario as it was designed when the scenario was run and the error occurred. I have some options here for clicking into the error and reviewing the reason for the interruption. I can also click on my trigger module and on the next module to get more information about the bundle which was passed through the scenario causing the error. Other options include adding more bundles to my scenario for this specific run. You also have the option of pulling up the Workfront Fusion Dev Tool, going to the Live Stream, and then clicking Run once again. This will give you more information as far as the request and the response headers and the bodies sent causing the error.

You can click through these if you want, review the information, and see if they can give you more clues as far as what might help resolve the error.

But I know that the project ID is missing. The light bulb goes off. I realize I’ve made an obvious mistake. So what I can do is I can click into that specific module, find the project ID area, and then I can go to my test drive and I can copy the project ID there, come back and put it in the project ID of the module, click OK, and this will fix the error and resolve the error of this specific bundle.

I’ll click Run once, and what you’ll notice is after it runs, it will pull you out of that correction area, and you’ll see at the right-hand side possibly an error attempt if you were playing around with it or a successful attempt at resolving this error.

If I go into the Incomplete Execution section, you can see that this specific record at the top has been resolved with one attempt.

There are a couple of different places where you can go to review and resolve incomplete executions. Of course, you can always come into a scenario and go to the Incomplete Executions tab to view the incomplete execution history log and click into the details to resolve that issue, as we did in the last video. Other options are going to the History tab for executions and any execution log labeled as a warning will be storing incomplete executions, in comparison to an error, which is just an error on a specific module, not logged as an incomplete execution. From this point, I can click on an errored execution or a warning execution.

I can see the warning in the designer, and then I can click Resolve, which pulls me back over to the incomplete execution in that specific record. My other options are to go to my personal profile settings, going to Email Notifications, and making sure that I toggle on the types of email notifications I want to receive from the system. And right above my name on the left-hand panel is a notifications area that will indicate when errors occur in my scenarios. I can click into this error, and it gives me a variety of information. What’s most useful is that my scenario, organization, team, and specific execution are all hyperlinked. Clicking on one of these hyperlinks will bring me to that incomplete execution history. -