Forcing a workflow to stop
If you force stop a workflow, this will interrupt the current active step. To stop a workflow after the current active step is complete, follow this guide.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID>
command. You can specify a different folder using the --folder-name
or --folder-id
parameter.
-
See the description of the CLI command to force stop a workflow:
yc serverless workflow execution terminate --help
-
Specify a workflow ID to get a list of workflow executions:
yc serverless workflow execution list --workflow-id <workflow_ID>
Result:
executions: - id: dfq...e78 workflow_id: dfqud9cbc4k5******** status: FINISHED started_at: "2025-03-10T15:54:44.304781814Z" duration: 1.070697344s ... - id: dfq...4d5 workflow_id: dfqud9cbc4k5******** status: FINISHED started_at: "2025-03-10T15:05:19.982768956Z" duration: 0.971907165s
-
Force a workflow to stop:
yc serverless workflow execution terminate <workflow_execution_ID>
Result:
execution_id: dfqmeu8ci1ae2tvocsbv-429e9f6f-b506-4c5a-84b2-9abb********
To force stop a workflow, use the terminate REST API method for the Execution resource or the ExecutionService/Terminate gRPC API call.