doctl harness-runtime triggers update

Generated on 6 Oct 2026 from doctl version v1.178.0

Usage

doctl harness-runtime triggers update <trigger-id> [flags]

Description

Update a trigger. Only flags you pass are changed. Kind and webhook provider cannot be changed.

--spec or --from-config replaces the session template for fresh triggers, with the same copy-not-link caveat as create: re-supply any secret values with --secret.

Example

doctl harness-runtime triggers update TRIGGER_ID --status paused;

Flags

Option Description
--bound-session-id Updated bound session ID for reuse triggers
--cron-expr Updated cron expression
--format Columns for output in a comma-separated list. Possible values: TriggerID, Name, Kind, Status, SessionMode, AgentKind, BoundSessionID, WebhookURL, NextRunAt, CreatedAt.
--from-config Name or ID of an existing Agent Config whose manifest becomes this trigger’s session template, instead of –spec.
--help, -h Help for this command
--name New unique trigger name (same identifier rules as create)
--no-header Return raw data with no headers
Default: false
--output-email Destination email when output-mode=email
--output-mode Output delivery mode (none|email|slack)
--output-slack-webhook Slack incoming webhook URL when output-mode=slack
--prompt Updated prompt template
--secret Tenant secret as NAME=VALUE, injected into the manifest’s secret slots (overriding a value declared in the file). Repeatable. NAME=@path reads the value from a file and NAME=- reads it from stdin, so a credential need not appear in shell history or in checked-in YAML.
--spec Updated agents.yaml manifest for fresh triggers ("-" reads stdin). ${VAR} references are resolved from the local environment at update time and stored expanded.
--status Lifecycle status (active|paused)
--timezone Updated IANA timezone
Command Description
doctl harness-runtime triggers Manage webhook and cron triggers for hosted agent runs

Global Flags

Option Description
--access-token, -t API V2 access token
--api-url, -u Override default API endpoint
--config, -c Specify a custom config file
Default:
    --context Specify a custom authentication context name
    --http-retry-max Set maximum number of retries for requests that fail with a 429 or 500-level error
    Default: 5
    --http-retry-wait-max Set the minimum number of seconds to wait before retrying a failed request
    Default: 30
    --http-retry-wait-min Set the maximum number of seconds to wait before retrying a failed request
    Default: 1
    --interactive Enable interactive behavior. Defaults to true if the terminal supports it (default false)
    Default: false
    --output, -o Desired output format [text|json]
    Default: text
    --trace Show a log of network activity while performing a command
    Default: false
    --verbose, -v Enable verbose output
    Default: false

    We can't find any results for your search.

    Try using different keywords or simplifying your search terms.