Skip to main content
All CollectionsGain Insights
Activity Log: Monitor Workflow Executions in Torq
Activity Log: Monitor Workflow Executions in Torq

Track workflow executions in the Activity Log, along with single-step executions and events that didn’t trigger workflows.

Updated over a month ago

Navigate to the Activity Log to follow past workflow executions. The Activity Log includes information on triggered workflows, single-step executions, and events received that did not trigger a workflow.

Display the response JSON of each run by clicking the drop-down arrow in the workflow's row. The response JSON depends on the activity type (all, workflow_runs, step_executions, etc.).

Activity logs can also be collected and passed to third parties, such as Elsasticsearch or AWS. See this template for a guideline on creating a nested workflow to collect the Torq Activity Logs or Audit Logs.

Understand Workflow Statuses

The workflow status represents the status of the current or most recent workflow execution. They are displayed in the status column of the Activity Log page.

Status

Description

The workflow execution was completed successfully.

A step failed, causing the workflow to fail. Hover over the information icon to see the name of the step that failed. View the run log to get more information about the failed step.

The workflow is currently running.

The workflow was manually stopped.

There are a few reasons a workflow might be on hold:

  • The workflow is waiting due to a Wait operator executing.

  • The parent workflow is on hold while a nested workflow is executing.

  • The workflow is waiting for user input (for example, a response from a question step or Torq Interact).

The maximum number of concurrent workflow runs (workflows in Running status) was reached.

A workflow that was queued for 24 hours will be dropped.

Did this answer your question?