doctl gradient simulation-run get-journey
Generated on 1 Sep 2026
from doctl version
v1.168.0
Usage
doctl gradient simulation-run get-journey <run-uuid> <journey-uuid> [flags]Aliases
g-jDescription
Retrieves a single journey of a simulation run, including: - The journey UUID - The UUID of the scenario the journey exercises - The journey index within the scenario - The journey status and judge verdict - The journey duration in seconds - The journey creation timestamp
Example
The following example retrieves a journey:
doctl gradient simulation-run get-journey f81d4fae-7dec-11d0-a765-00a0c91e6bf6 6ba7b810-9dad-11d1-80b4-00c04fd430c8Flags
| Option | Description |
|---|---|
--format |
Columns for output in a comma-separated list. Possible values: UUID, ScenarioUUID, JourneyIndex, Status, Verdict, DurationSec, CreatedAt. |
--help, -h |
Help for this command |
--no-header |
Return raw data with no headers Default: false |
Related Commands
| Command | Description |
|---|---|
| doctl gradient simulation-run | Display commands that manage Gradient AI simulation 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 |