Viewing flow history

The History tab provides troubleshooting information for a flow.

With flow history, you can:

  • filter the flows for which you want to see information by the name and status of flows.

  • view the status of all or selected flow runs.

  • view the status, version, name, timestamp, and additional information such as whether the flow was replayed for each flow run.

    • the status can be: Success, Error, Pending (delayed), or Scheduled. Scheduled indicates that the flow action is scheduled using the Schedules utility.

    • additional information can be Replayed, or Compilation error at step number.

  • click a flow run to view the steps in the flow and their status. From the step view:

    • to return to the flow list, click Back.

    • to move between flow runs, click Next or Previous.

    • to run the flow again with the same data, click Rerunflow.

      Note  You can't rerun a flow that is triggered by the Schedules utility.

  • click a step to view the HTTP request and response. (Trigger steps only contain a request.)

    Note  The body of the requests and responses will be empty if saving request and response data is turned off.

Claris Connect Flow History, HTTP response and step status

The HTTP request shows the HTTP method, body, and URL parameters. This page also shows the success or error status and the request URL. If there are any errors, the response displays the error.

Note  You can't view information for any steps that didn't run.

If saving request and response data is turned on, Claris Connect saves the request and response data for all the flow runs in a project for 30 days. Saving request and response data is turned on or off for all flows in a project.

To change the option for saving request and response data:

  1. On the Flows page of a project, click the History tab.

  2. Use the slider at the bottom of the screen to turn on or off saving request and response data.

Important  Saving request and response is off by default. After the option is turned on, turning it off again deletes all request and response data from the project and cannot be undone.