SLA & automation

How the SLA clock runs

SLA targets are stored in hours. The clock runs around the calendar but skips the workspace's configured weekend days, evaluated in the workspace timezone. Per-priority defaults are set in Settings → SLA defaults and applied when a request or task doesn't specify its own target.

The clock is weekend-aware calendar hours — FlowX does not currently compute business-hours-only SLAs.

Overdue is a flag

Breaching a deadline never rewrites the status. Overdue items keep their real status and gain an overdue flag; background scans record breaches, notify, and escalate in stages.

Status automation

Each rule is a workspace toggle in Settings → Workflow.

• Auto-start on activity — a New task or request moves to In Progress when real work begins (requests wait for approval first).
• Start requests once approved — an approved request can move to In Progress automatically.
• Recover from delay — moving a deadline into the future clears the overdue flag without touching the status.

On mobile

SLA state is visible everywhere, including mobile. Configuring SLA targets and automation rules is web-only, for administrators.