Reviewing a Flow Execution

Created by Brian Glick, Modified on Tue, 4 Nov at 9:27 AM by Brian Glick

Once you've found a Flow Execution that you want to review in the flow search screen, you can click view to see the execution details.  All the information you need is in one page for a complete snapshot of the transaction.


Actions

The actions section has buttons you can click to complete task related to the flow.  Depending on your permissions, you may see all or some of these actions.


  • Resubmit
    Resubmits the data from this execution creating a new Flow Execution. Use this to reprocess data.

  • Flag
    Adds the flow execution to the Flagged Flows section of the integration dashboard so you can quickly find it later.

  • Share
    Makes the Files & Logs sections available to integration users. Be cautious with this feature as your files may contain confidential data you don't want your trading partner to see.
  • Settings
    This is a shortcut link to the setup screen for this flow.

  • Linked Executions
    If this flow was the result of resubmitting another flow or this flow has been resubmitted, then you will find quick links to those executions here.


AI Summary

Click the AI Summary button to get a plain English interpretation of everything that happend within the flow execution.  This is especially helpful when your flow has large log messages returned from other systems or technical error codes that you do not understand.


Summary

This section has key information about your flow including it's final status, summary message, name, and flow type.


Timings

  • Duration
    This is how long your flow took to run from the time it started to when it ended (not including any time it was queued for processing)

  • Submitted 
    This is the time that your flow's data was received by Chain.io and the Flow Execution record was created. There may be a delay between the submitted time and start time due to queuing and throttling that you have configured for your flow or host system. These queues prevent other systems from being overloaded if you receive data faster than they can handle.

  • Started
    This is the time that Chain.io began processing your flow data after any queues were cleared.

  • Ended
    This is the time that the flow execution completed processing.


Data Tags

Data tags represent the key busienss data related to your Flow Execution like reference numbers, port codes, part numbers, or bills of lading.  Different data tags are written depending on your flow configuration.  These values are also searchable in Flow Search. You can click the copy button next to any data tag to copy the value to your clipboard.


Identifiers

Identifiers are the unique values that Chain.io support can use to help you identifiy a particular Flow Execution.  They are also utilized if you use our GraphQL API to programatically interact with a Flow Execution.


Notifications

The notifications section shows a record of any emails or webhooks that were triggered notifying parties about the final status of your flow execution.  You can configure notifiers in your flow setup or in the workspace setup screens for global notifications.


Configuration

The configuration section shows a brief summary of the components of your flow which were configured in your flow setup.


Files


If you are an integration user and the owner of the flow has not configured auto-share, then you will not see the files and logs. This is done to hide potentially confidental data.  If you need to see the files and logs for any particular execution, an owner or editor for the workspace can click the Share button in the Actions section to make that data available to you.


The files section shows the data received by the flow, any subsequent transformations, as well as the server response from any APIs called when the data was delivered.  You can view or download any file.  


Logs

Logs contain the detailed processing logs from the various components that ran within the flow as well as any responses from remote systems called by the flow.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article