rwx retry
Retry a run or task.
Usage
rwx retry [flags]
rwx retry infers whether the ID belongs to a run or to a task. Two noun-verb
forms declare the target explicitly:
rwx runs retry [flags]
rwx tasks retry [flags]
All three forms accept the same flags and behave the same way.
Description
rwx retry requests a retry from RWX. The available retry actions depend on the
target and on its current state, so the CLI reads them from RWX first.
When exactly one action is available, the CLI uses it. When several are
available, an interactive terminal prompts you to choose one. Otherwise the CLI
prints the available actions and exits, so you can rerun the command with
--action.
Examples
Retry a run and choose an action interactively:
rwx retry f068b078bca8b14180335cde89859698
Retry only the tasks that failed:
rwx retry --action failures f068b078bca8b14180335cde89859698
Retry a task and open a breakpoint before it runs:
rwx tasks retry --action standard --debug start 3a1c9d0e5f27418ab6c4d8e9f0123456
Retry without a tool cache:
rwx retry --action no-tool-cache --without-tool-cache node-modules f068b078bca8b14180335cde89859698
Arguments
<run-or-task-id> (required)
The ID of the run or task to retry. You can find both IDs in the URL when you
view a run in the RWX UI. You can also list recent runs and their IDs with
rwx runs list.
Options
--action <action>
The retry action to use. RWX offers these built-in values:
| Action | Applies to | Behavior |
|---|---|---|
standard | Runs and tasks | Every task that ran will run again. Tasks that were cache hits will try to cache hit again. Tasks that were previously retried using a custom retry action (such as retrying only failed tests) will use the same retry action again. |
failures | Runs | Every task that failed will run again. |
clean | Runs and tasks | Every task that ran will run again. Tasks that were cache hits will try to cache hit again. Any tasks previously retried using a custom action (such as retrying only failed tests) will start over with a clean slate. |
no-tool-cache | Runs and tasks | Choose one or more tool caches to exclude. Only affected tasks will run again. |
A task can also publish its own actions. Pass one as
custom:<retry-action-key>, where the key is the directory name you wrote under
$RWX_RETRY_ACTIONS. See Retry actions.
Not every action is available for every target. Run the command without
--action to see the current list.
--without-tool-cache <name>
The name of a tool cache to exclude. Can be specified multiple times. This flag
requires --action no-tool-cache.
--debug <placement>
Open a breakpoint at the start or end of the retried task. Pass start or
end. A breakpoint needs a specific task, so this flag does not apply when the
target is a run. See Remote debugging.
Global options
--format <format>
Output format: text or json. Defaults to text.
json mode is not interactive. When the target needs an action and you did not
pass one, the CLI reports the available options instead of prompting.
--json
Output JSON data to stdout. Equivalent to --format json.
--access-token <token>
The access token for RWX. Defaults to the value of the $RWX_ACCESS_TOKEN environment variable.