On-call schedules

DevFlow doesn't replace your PagerDuty / Opsgenie schedule — it routes alerts into them. But for teams that don't have a dedicated paging tool, DevFlow has its own minimal schedule primitive.

creating a schedule

schedule:
  name: payments-oncall
  timezone: America/New_York
  rotation:
    type: weekly
    handoff: monday-09:00
    members:
      - priya@example.com
      - rohan@example.com
      - amaia@example.com
  fallback:
    after_minutes: 15
    members:
      - oncall-manager@example.com

handoffs

The handoff time is in the schedule's timezone. The outgoing on-call gets a Slack DM (or email) 30 minutes before, with a bullet of the open incidents.

working-hours-only schedules

Some teams (back-office services) only want pages during business hours. The fallback in those cases is a Slack channel:

schedule:
  name: backoffice-business-hours
  timezone: Europe/Lisbon
  working_hours: { start: "09:00", end: "18:00", days: [Mon, Tue, Wed, Thu, Fri] }
  outside_hours:
    fallback:
      channels: [slack:#backoffice-async]

who shouldn't be paged

New hires shouldn't be on call until they've completed team-onboarding and shadowed at least one incident. Set their start date in the rotation explicitly.

acknowledging and resolving

When an alert fires, the on-call can ack from PagerDuty, the DevFlow dashboard, or replying /ack in the Slack thread. See incident-management.