v2.6.34
Resolved incidents keep their full window on the status page
- 1new
- 1fixed
Status updates can now record an incident that has already ended: the status page shows the incident from its start to its resolved time, and the timeline keeps overlapping incidents correct. Existing API requests, responses, webhooks and bot behaviour are unchanged.
New Features
- Resolved incident windows — a status update can now carry an end time. Publish an incident that is already over with its start and resolved time, and status.meetingbaas.com shows the full window instead of only when it was opened. A scheduled maintenance window closes automatically at its end time.
Bug Fixes
- The status page no longer clears a newer incident when an older, overlapping incident is resolved. The most recent update stays in effect until it is resolved or a newer update supersedes it, and the 30-day history follows the same timeline.