GLOBUS TASK PAUSE-INFO

NAME

globus task pause-info - Show why an in-progress task is currently paused

SYNOPSIS

globus task pause-info [OPTIONS] TASK_ID

DESCRIPTION

Show messages from activity managers who have explicitly paused the given in-progress task and list any active pause rules that apply to it.

This command displays no information for tasks which are not paused.

OPTIONS

-v, --verbose

Control level of output

-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. Takes precedence over any specified '--format' and 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"

OUTPUT

When text output is requested, output is broken apart into explicit pause rules applied to the specific task (explicit pauses), and "effective pause rules" which apply to the task by virtue of the endpoint(s) it uses.

Explicit pauses are listed with any of the following fields which apply:

  • 'Source Endpoint'

  • 'Source Shared Endpoint'

  • 'Destination Endpoint'

  • 'Destination Shared Endpoint'

which refer to the messages which may be set by these various endpoints.

Effective pause rules are listed with these fields:

  • 'Operations'

  • 'On Endpoint'

  • 'All Users'

  • 'Message'

EXAMPLES

Show why a task is paused, producing JSON output:

$ globus task pause-info TASK_ID --format JSON

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.