GLOBUS TASK SHOW

NAME

globus task show - Show detailed information about a task

SYNOPSIS

globus task show [OPTIONS] TASK_ID

DESCRIPTION

Print information detailing the status and other info about a task.

The task may be pending, completed, or in progress.

OPTIONS

-t, --successful-transfers

Show files that were transferred as result of this task. Mutually exclusive with --skipped-errors

--skipped-errors

Show paths that were skipped due to errors during this task. Mutually exclusive with --successful-transfers

-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 varies slightly between 'TRANSFER' and 'DELETE' tasks, and between active and completed tasks.

All of the following which apply will be shown:

  • 'Task ID'

  • 'Type'

  • 'Status'

  • 'Is Paused'

  • 'Label'

  • 'Files'

  • 'Directories'

  • 'Source Endpoint'

  • 'Source Endpoint ID'

  • 'Destination Endpoint'

  • 'Destination Endpoint ID'

  • 'Endpoint'

  • 'Endpoint ID'

  • 'Completion Time'

  • 'Deadline'

  • 'Details'

  • 'Request Time'

  • 'Bytes Transferred'

  • 'Bytes Per Second'

  • 'Faults'

  • 'Total Subtasks'

  • 'Subtasks Succeeded'

  • 'Subtasks Pending'

  • 'Subtasks Retrying'

  • 'Subtasks Failed'

  • 'Subtasks Canceled'

  • 'Subtasks Expired'

If --successful-transfers is given, the following fields are used:

  • 'Source Path'

  • 'Destination Path'

EXAMPLES

Show detailed info about a task as text

$ globus task show TASK_ID

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.