# Nester Workflow Overview

For some activations, you might want the output to be processed with a workflow job before the output is exported. For such use cases, you can configure an activation to trigger a workflow after the activation is run. This configures the triggered workflow as an integral part of the activation; the overall status of the activation is tied to this nested workflow. The activation would have a successful status only when both the activation and triggered workflow are successful.

A nested workflow can only be a user-defined workflow, not a system-generated one.

## Sequential Activation

Multiple activations using the same authentication can run in parallel onto an external output account. It might not be suitable for activations with nested workflow to run in parallel because the workflows involve processing output data. If you want to prevent a parallel run, you can enable Sequential Activation for activations with nested workflow. This ensures that any sequential-enabled activation does not run in parallel with matched activations. Matched activations are all sequential-enabled activations that share the same authentication. The matched activations run one at a time in sequence and, therefore, avoid a parallel run.

Activations that do not have Sequential Activation enabled run promptly without any check of other activations, whether sequential-enabled or not.