Skip to main content

Sending Signals to Workflows

You can manage and automate workflows by sending signals to pause, resume, terminate, restart, rerun workflows, and more. Using Conductor SDKs or APIs, you can integrate and programmatically control workflows during production and in case of failure.

Pause workflow

You can pause a workflow to wait for external signals.

In the workflow execution page (Executions > Workflow > someWorkflow), select Actions > Pause.

Pausing workflows from UI

Resume workflow

Once an external signal is received, you can resume the paused workflow.

In the workflow execution page (Executions > Workflow > someWorkflow), select Actions > Resume.

Resuming workflows from UI

Restart workflow

If a workflow execution fails for any reason and enters a terminal state, you can restart it from the beginning. There are two options for restarting workflows:

  • Restart with Current Definitions—Restart using the same workflow definition that was referenced in the initial execution. This is useful if the workflow definition has changed and the original definition needs to be retained.
  • Restart with Latest Definitions—Restart using the latest workflow definition and version. If you’ve changed the definition, you can use this option to rerun the execution with the latest version.
note

When restarting workflows, the same inputs will be used. To use different workflow inputs, rerun the workflow instead.

In the workflow execution page (Executions > Workflow > someTerminalWorkflow), select Actions > Restart with current definitions or Restart with latest definitions.

Restarting workflows from UI

Rerun workflow

You can rerun a terminal workflow from the start if you need to change the workflow inputs, correlation ID, or task-to-domain mapping. The workflow (execution) ID from the original run will be retained.

note

In the UI, there is no option to rerun the workflow using the same workflow (execution) ID. However, you can rerun it by creating a new execution instance.

In the workflow execution page (Executions > Workflow > someTerminalWorkflow), select Actions > Re-run Workflow. You will be redirected to the Run Workflow page, where you can update the workflow inputs, correlation ID, and task-to-domain mapping to run a new workflow instance.

Rerun workflow in Conductor UI

Rerun workflow from task

In certain cases, you may wish to rerun an ongoing or terminal workflow from a specific task instead.

In the workflow execution page (Executions > Workflow > someWorkflow), select a task in the visual diagram, then select Re-Run from Task. The task will be rerun, and the previous attempt(s) will be marked as CANCELED.

Rerun workflow from task in Conductor UI

note

If you need to provide updated task inputs, use the API instead.

Retry from failed task

If the workflow fails, you can retry it from its last failed task.

In the workflow execution page (Executions > Workflow > someWorkflow), select Actions > Retry - from failed task. The task will be rerun, and the previous attempt(s) will be marked as CANCELED.

Retry from Conductor UI

Update task status

In some cases, you may need to update the task status in an ongoing workflow with a signal, such as updating the status of a signal-type Wait task.

  1. In the workflow execution page (Executions > Workflow > someWorkflow), select a task in the visual diagram.
  2. In the Summary tab, select a status in the Update task field.
  3. (Optional) Add the task outputs in the Code field.
  4. Select Update.

Once the task is updated via UI,the worker is automatically set to conductor-ui, providing better traceability for manual overrides.

Update a task's status in Conductor UI

Terminate workflow

In some cases, you may need to terminate the workflow with a signal. For example, if a user terminates an ongoing indexing process.

In the workflow execution page (Executions > Workflow > someWorkflow), select Actions > Terminate.

Terminate workflow from Conductor UI