Flow monthly SLA report
Flow has active blockers in the current report window and should stay in recovery mode until the release evidence turns green. · Tenant: global · Window: 30 days · Source: public
Report recovery path
If the report shows issues, jump straight to incident recovery. If it is clear, publish the pack and share it with customers or sales.
Review incidents, release evidence and the current monthly signal in one lane.
Route blockers into incident history or the reliability console before the report is shared.
Publish the report pack once the signal is clean and the recovery path is green.
Monthly reports should stay readable for customers, while the admin session unlocks the daily snapshot and release evidence layer.
insufficient test data
Customer-visible state right now.
insufficient test data
What the current recovery window looks like.
0%
Current execution pulse from public status.
0
Daily snapshots in the report window.
0
Artifact-backed release evidence rows.
0 / 0
Days ready versus blocked in this report window.
Work next
Stable history can be shared as a customer-facing SLA pack.
Export report pack
The report should move someone toward recovery, not just give them a PDF-shaped summary.
Average health insufficient test data · Average execution insufficient test data · Health trend insufficient test data
| Commitment | Current | State | Note |
|---|---|---|---|
| Uptime | insufficient test data | watch | No public SLA payload available yet. |
Customer-facing format: date, impact, resolution note and the matching artifact evidence.
| Date | Status | Health | Execution | Queue | Payments | Security | Resolution note | Evidence |
|---|---|---|---|---|---|---|---|---|
| insufficient test data | ||||||||
Artifact-backed evidence used for the monthly report.
| Generated | Status | Scope | Artifact | Blockers | Summary |
|---|---|---|---|---|---|
| insufficient test data | |||||
The customer-visible surface is stable and can be used without asking support.
Publish the next update at the scheduled recovery time.
The latest release evidence is blocked and needs another snapshot after blockers are cleared.
Use the reliability console to capture a fresh snapshot after fixing blockers.
No incident timeline entries were available for the current report window.
Keep the incident history page aligned with the published SLA report.