> For the complete documentation index, see [llms.txt](https://docs.gradient.works/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gradient.works/kb/automation-builder-kit-abk/actions/flow-lifecycle/resumeflowaction.md).

# Resume

Pair this with [Start](/kb/automation-builder-kit-abk/actions/flow-lifecycle/startflowaction.md) and [Finish](/kb/automation-builder-kit-abk/actions/flow-lifecycle/finishflowaction.md) actions. Use this action after a Screen Flow action to resume execution tracing for individual executions of the Flow ("interviews" in Flow-speak). Screen Flow actions can cause the transaction for the Flow execution to change which makes execution tracing difficult. Resuming tracking of the original transaction from the [Start](/kb/automation-builder-kit-abk/actions/flow-lifecycle/startflowaction.md) will allow us to continue to track the full Flow execution lifecycle.

## Inputs

| Name              | Required | Type   | Description                                                                                                                         |
| ----------------- | -------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| flowInterviewGuid | Yes      | String | The interview GUID from the [Start](/kb/automation-builder-kit-abk/actions/flow-lifecycle/startflowaction.md) element in your Flow. |
| flowApiName       | No       | String | The API name of the flow                                                                                                            |

## Outputs

| Name              | Type   | Description        |
| ----------------- | ------ | ------------------ |
| flowInterviewGuid | String | The interview GUID |