guild runs restore [OPTIONS] [RUN...]
Restore one or more deleted runs.
Runs are restored using
RUN arguments. If a
RUN argument is not specified, all runs matching the filter criteria are restored. See SPECIFYING RUNS and FILTERING topics for more information.
guild runs list --deleted for a list of runs that can be restored.
By default, Guild will display the list of runs to be restored and ask you to confirm the operation. If you want to restore the runs without being prompted, use the
You may use one or more
RUN arguments to indicate which runs apply to the command.
RUN may be a run ID, a run ID prefix, or a one-based index corresponding to a run returned by the list command.
Indexes may also be specified in ranges in the form
START is the start index and
END is the end index. Either
END may be omitted. If
START is omitted, all runs up to
END are selected. If
END id omitted, all runs from
START on are selected. If both
END are omitted (i.e. the
: char is used by itself) all runs are selected.
RUN argument is not specified,
: is assumed (all runs are selected).
Filter by Operation or Label
Runs may be filtered by operation using
--operation. A run is only included if any part of its full operation name, including the package and model name, matches the value.
--label to only include runs with labels matching a specified value.
--label may be used multiple times to expand the runs that are included.
--unlabeled to only include runs without labels. This option may not be used with
--marked to only include marked runs.
Filter by Run Status
Runs may also be filtered by specifying one or more status filters:
--terminated. These may be used together to include runs that match any of the filters. For example to only include runs that were either terminated or exited with an error, use
--terminated --error, or the short form
Status filters are applied before
RUN indexes are resolved. For example, a run index of
1 is the latest run that matches the status filters.
Filter by Run Start Time
--started to limit runs to those that have started within a specified time range.
IMPORTANT: You must quote RANGE values that contain spaces. For example, to filter runs started within the last hour, use the option:
--selected 'last hour'
You can specify a time range using several different forms:
between DATETIME and DATETIME
last N minutes|hours|days
N days|weeks|months|years ago
DATETIME may be specified as a date in the format
YY-MM-DD (the leading
YY- may be omitted) or as a time in the format
HH:MM (24 hour clock). A date and time may be specified together as
between DATETIME and DATETIME, values for
DATETIME may be specified in either order.
When specifying values like
hours the training
s may be omitted to improve readability. You may also use
min instead of
hr instead of
between 1-1 and 4-30
between 10:00 and 15:00
last 30 min
last 6 hours
3 weeks ago
Filter by Source Code Digest
To show runs for a specific source code digest, use
--digest with a complete or partial digest value.
Restore Remote Runs
If a run has been deleted remotely, you can restore it using
--remote provided the remote type supports this feature.
REMOTE is the name of a configured remote. Use
guild remotes to list available remotes.
For information on configuring remotes, see
||Filter runs with operations matching
||Filter runs with labels matching
||Filter only runs without labels.|
||Filter only marked runs.|
||Filter only unmarked runs.|
||Filter only runs that are still running.|
||Filter only completed runs.|
||Filter only runs that exited with an error.|
||Filter only runs terminated by the user.|
||Filter only pending runs.|
||Filter only staged runs.|
||Filter only runs started within RANGE. See above for valid time ranges.|
||Filter only runs with a matching source code digest.|
||Restore remote runs.|
||Do not prompt before restoring.|
||Show this message and exit.|
Guild AI version 0.7.0.post1