GLOBUS TIMER CREATE FLOW

NAME

globus timer create flow - Create a recurring flow timer.

SYNOPSIS

globus timer create flow [OPTIONS] FLOW_ID

DESCRIPTION

Create a timer that runs a flow on a recurring schedule.

Examples (assume the year is 1970, when time began):

Create a timer which runs a flow daily for the next 10 days.

globus timer create flow $flow_id --interval 1d --stop-after-runs 10

Create a timer which runs a flow every week for the rest of the year.

globus timer create flow $flow_id --interval 7d --stop-after-date 1970-12-31

Create a timer which runs a flow once on Christmas.

globus timer create flow $flow_id --start 1970-12-25 --stop-after-runs 1

OPTIONS

--input [JSON_FILE|JSON|file:JSON_FILE]

The JSON input parameters used to start the flow.

The input document may be specified inline, or it may be a path to a JSON file, prefixed with "file:".

Example: Inline JSON:

--input '{"src": "~/source"}'

Example: Path to JSON file:

--input parameters.json

If unspecified, the default is an empty JSON object ('{}').

--name TEXT

A name for the timer.

--start [%Y-%m-%d|%Y-%m-%d %H:%M:%S|%Y-%m-%d %H:%M:%S%z|%Y-%m-%dT%H:%M:%S|%Y-%m-%dT%H:%M:%S%z|%Y-%m-%dT%H:%M:%S.%f%z]

Start time for the timer. Defaults to current time.

--interval TIMEDELTA

Interval at which the timer should run. Expressed in weeks, days, hours, minutes, and seconds. Use 'w', 'd', 'h', 'm', and 's' as suffixes to specify. e.g. '1h30m', '500s', '10d'

--stop-after-date [%Y-%m-%d|%Y-%m-%d %H:%M:%S|%Y-%m-%d %H:%M:%S%z|%Y-%m-%dT%H:%M:%S|%Y-%m-%dT%H:%M:%S%z|%Y-%m-%dT%H:%M:%S.%f%z]

Stop running the transfer after this date.

--stop-after-runs INTEGER RANGE

Stop running the transfer after this number of runs have happened. [x>=1]

-v, --verbose

Control level of output, make it more verbose.

--quiet

Suppress non-essential output. This is higher precedence than --verbose.

-h, --help

Show this message and exit.

-F, --format [unix|json|text]

Output format for stdout. Defaults to text.

--jmespath, --jq TEXT

A JMESPath expression to apply to json output. Forces the format to be json processed by this expression.

--map-http-status TEXT

Map HTTP statuses to any of these exit codes: 0,1,50-99. e.g. "404=50,403=51"

EXIT STATUS

0 on success.

1 if a network or server error occurred, unless --map-http-status has been used to change exit behavior on http error codes.

2 if the command was used improperly.

3 if the command was used on the wrong type of object, e.g. a collection command used on an endpoint.

4 if the command has authentication or authorization requirements which were not met, as in ConsentRequired errors or missing logins.