gcloud tasks create-app-engine-task Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud tasks create-app-engine-task - create and add a task that targets App Engine
- SYNOPSIS
gcloud tasks create-app-engine-task[TASK_ID]--queue=QUEUE[--header=HEADER_FIELD:HEADER_VALUE][--location=LOCATION][--method=METHOD][--relative-uri=RELATIVE_URI][--routing=KEY:VALUE,[…]][--schedule-time=SCHEDULE_TIME][--body-content=BODY_CONTENT|--body-file=BODY_FILE][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
- Create and add a task that targets App Engine.
- EXAMPLES
- To create a task:
gcloudtaskscreate-app-engine-task--queue=my-queue--relative-uri=/handler-pathmy-task - POSITIONAL ARGUMENTS
- [
TASK_ID] - The task to create.
If not specified then the system will generate a random unique task ID.Explicitly specifying a task ID enables task de-duplication. If a task's ID isidentical to that of an existing task or a task that was deleted or completedrecently then the call will fail.
Because there is an extra lookup cost to identify duplicate task names, taskscreated with IDs have significantly increased latency. Using hashed strings forthe task ID or for the prefix of the task ID is recommended.
- [
- REQUIRED FLAGS
--queue=QUEUE- The queue the task belongs to.
- OPTIONAL FLAGS
--header=HEADER_FIELD:HEADER_VALUE- An HTTP request header. Header values can contain commas. This flag can berepeated. Repeated header fields will have their values overridden.
--location=LOCATION- The location where we want to manage the queue or task. If not specified, usesthe location of the current project's App Engine app if there is an associatedapp.
--method=METHOD- The HTTP method to use for the request. If not specified, "POST" will be used.
--relative-uri=RELATIVE_URI- The relative URI of the request. Must begin with "/" and must be a valid HTTPrelative URI. It can contain a path and query string arguments. If notspecified, then the root path "/" will be used.
--routing=KEY:VALUE,[…]- The route to be used for this task. KEY must be at least one of: [service,version, instance]. Any missing keys will use the default.
Routing can be overridden by the queue-level
--routing-overrideflag. --schedule-time=SCHEDULE_TIME- The time when the task is scheduled to be first attempted. Defaults to "now" ifnot specified.
- At most one of these can be specified:
--body-content=BODY_CONTENT- HTTP Body data sent to the task worker processing the task.
--body-file=BODY_FILE- File containing HTTP body data sent to the task worker processing the task.
- 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 helpfor details. - NOTES
- These variants are also available:
gcloudalphataskscreate-app-engine-taskgcloudbetataskscreate-app-engine-task
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.