Globus Timers
Globus Timers provides a simple way to schedule asynchronous tasks. A timer can be used to schedule specific operations to occur at a particular time or to repeat at regular intervals. The Globus Timers service currently supports scheduling of flow runs and transfer tasks.
A timer is a definition of an operation to be performed and a schedule for when to perform it. Each time a timer's schedule condition is reached, a timer run is created. A timer run records the result of an operation, tracking its progress through completion.
Getting Started
The best way to get started is to try creating a timer. See the Scheduling a Transfer or Scheduling a Flow Run tutorials for a step-by-step guide to creating your first timer.
Understanding Timer Schedules
For more information on timer behaviors and scheduling options, the Timer Schedules document provides an overview of the options available when creating a timer, information about how timers behave in different situations, as well as instructions for pausing and resuming your timers.
Limits
The Globus Timers service has the following usage limits:
-
A user’s timers cumulatively cannot run more often than once per minute.
-
Only the last 90 days of activity are retained for a timer.
CLI, SDK, and APIs
Globus Timers is supported in the Globus CLI and the Globus Python SDK.
-
Globus CLI: Timers Commands Install the Globus CLI to manage your timers.
-
Globus Python SDK The Globus Python SDK provides clients for interacting with your timers.
-
Globus Python SDK Examples Examples illustrating how to use the Globus Python SDK to create and manage timers.
-
Globus Timers API Specification The Globus Timers API reference documentation.