Skip to content

Every job has a run time limit. The limit used is the first one set, in this order:

  1. The stage (in the flow editor, Time limits)
  2. The launcher
  3. The project (Project Settings > Machines > Run time limit)
  4. The system default

No limit can go above the max: the project’s Max run time if set, otherwise the system default max. Nothing can go above the admin’s hard ceiling. A default above its max is lowered. Launches can’t exceed the max run time.

Use minutes, hours, or days. Blank means use the next level.

eureka session launch LAUNCHER --time 30m stores that limit. eureka session status shows 30:00 and 1800 seconds before the clock starts, and counts down after the session is running.

  • An app session follows its launcher’s At the time limit setting: Pause keeps the disk (the session is paused until you select Restart), Delete removes the machine and disk.
  • A Slurm job is stopped and shows TIMEOUT.
  • A flow stage that boots a machine (CPU, GPU, or a copy on its own transfer machine) is stopped and its machines are deleted.
  • This does not stop the work for a model, quantum, Vertex, Bedrock, or SageMaker call, a copy or script on the login node, or a job submitted to an external cluster: the stage is marked timed out, but the remote work is not cancelled.

System admins set the hard ceiling, max, and default on Time limits. That page covers the settings only; this page is the one place that explains how limits apply.