Telesales — StringeeX daily
SUSPENDED3 consecutive missed windows — auto-suspended 2026-09-22 05:00 +07. Every bound metric is now not_reported: the tiles are stale, and none of them can render green. A project failing repeatedly is producing noise, so the failure state is made louder than the data — and resuming takes a human and a note, not a retry.
Expiry warnings went to both owners at T‑30, and go again at T‑7 and T‑1. Both, not just the data owner — when a feed dies because a key lapsed, the person who has to explain the gap in the number is the metric owner.
Two keys may be active at once, overlapping for at most 30 days. That overlap is not a convenience — without zero-downtime rotation, the rotation never happens, and an eternal credential is the one nobody replaces.
- · An organisation-wide shared key. A Telesales key must not be able to write Finance numbers.
- · A credential that can both read and write. This one is push-only — it cannot read a single metric value.
- · An unlimited lifetime. 180 days by default, 365 at most.
- · “Resend me the same key.” Lost means rotate, never recover.
Each of these would be a one-line feature, and each would quietly undo the row-level security model in 04 §8. That is why they are listed as refusals rather than left unbuilt.