Job Scheduler

Plan recurring and one-off jobs with schedules, owners, runtimes, dependencies, retries, and failure visibility. This example brings Schedule and Jobs together so engineering teams can find the next task without losing context.

It includes representative records such as Nightly warehouse sync and Invoice generation. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Job Scheduler
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Schedule job

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to schedule job while keeping jobs, running and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Schedule gives users an obvious place to start.
  • Supporting view: Jobs keeps the related context close.
  • Primary action: Schedule job stays visible when people need it.
  • First signal: Jobs shows a useful value (84).
  • Second signal: Running gives additional context (7).
  • Sample record: Nightly warehouse sync.
  • Next record: Invoice generation.

States worth designing

  • No slots in selected range: say what changed, protect progress, and offer a clear next step.
  • Timezone mismatch: say what changed, protect progress, and offer a clear next step.
  • Booking conflict: say what changed, protect progress, and offer a clear next step.
  • Booking confirmed: say what changed, protect progress, and offer a clear next step.
  • Reschedule failure: say what changed, protect progress, and offer a clear next step.
  • View-only permission: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Schedule → Jobs → Schedule job → Review outcome

Patterns used

Calendar, Schedule, Jobs, contextual actions, error recovery

Why these choices work

Show the timezone, resource and conflicting time slots before confirmation. Recovery should preserve the selected date and context.

Pay attention to schedule and jobs. People need to distinguish Nightly warehouse sync from Invoice generation. Keep jobs visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Schedule job”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Queue Monitor, Certificate Management, Database Monitor.

Start from this in Figr

Design a job scheduler screen inside our existing product. Use our current components, tokens and content language. Include Schedule and Jobs views, credible records like Nightly warehouse sync, and a clear “Schedule job” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr