gcloud workflows execute

NAME
gcloud workflows execute - execute a workflow
SYNOPSIS
gcloud workflows execute(WORKFLOW :--location=LOCATION)[--call-log-level=CALL_LOG_LEVEL; default="none"][--data=DATA][--disable-concurrency-quota-overflow-buffering][--execution-history-level=EXECUTION_HISTORY_LEVEL; default="none"][--labels=[KEY=VALUE,…]][GCLOUD_WIDE_FLAG]
DESCRIPTION
Execute a workflow.
EXAMPLES
To execute a workflow named 'my-workflow' with the data that will be passed tothe workflow, run:
gcloudworkflowsexecutemy-workflow--data=my-data
POSITIONAL ARGUMENTS
Workflow resource - Name of the workflow to execute. The arguments in this groupcan be used to specify the attributes of this resource. (NOTE) Some attributesare not given arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumentworkflow on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

WORKFLOW
ID of the workflow or fully qualified identifier for the workflow.

To set theworkflow attribute:

  • provide the argumentworkflow on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--location=LOCATION
The Cloud location for the workflow. Alternatively, set the property[workflows/location].To set thelocation attribute:
  • provide the argumentworkflow on the command line with a fullyspecified name;
  • provide the argument--location on the command line;
  • set the propertyworkflows/location.
FLAGS
--call-log-level=CALL_LOG_LEVEL; default="none"
Level of call logging to apply during execution.CALL_LOG_LEVEL must be one of:
log-all-calls
Log all calls to subworkflows or library functions and their results.
log-errors-only
Log when a call is stopped due to an exception.
log-none
Perform no call logging.
none
No call logging level specified.
--data=DATA
JSON string with data that will be passed to the workflow as an argument.
--disable-concurrency-quota-overflow-buffering
If set, the execution will not be backlogged when the concurrency quota isexhausted. Backlogged executions start when the concurrency quota becomesavailable.
--execution-history-level=EXECUTION_HISTORY_LEVEL; default="none"
Level of execution history to apply during execution.EXECUTION_HISTORY_LEVEL must be one of:
execution-history-basic
Enable basic execution history.
execution-history-detailed
Enable detailed execution history, including expected iterations and in-scopevariable values.
none
No execution history level specified.
--labels=[KEY=VALUE,…]
List of label KEY=VALUE pairs to add.

Keys must start with a lowercase character and contain only hyphens,underscores, lowercase characters, and numbers. Values must contain onlyhyphens, underscores, lowercase characters, and numbers.

GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

API REFERENCE
This command uses theworkflowexecutions/v1 API. The fulldocumentation for this API can be found at:https://cloud.google.com/workflows
NOTES
This variant is also available:
gcloudbetaworkflowsexecute

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-07 UTC.