For platforms retiring an API version, an auth method or a payload
Sunset CensusName every integration that breaks on your date, and the person who can fix it - before you turn the old surface off.
List what retires and when, and every integration still calling it. Your browser classifies each one by the migrated rule - no old call for a full business-cycle lookback after the first new one, or written confirmation; one replacement call proves nothing; short logs leave a row unknown; dormant is not migrated - ranks them by days to break, then end customers affected, sizes the top tier by outreach hours, checks the door and verified contacts, and reads the five-line readiness gate. Then the outreach plan, and the go/no-go memo.
The sunset, and a short interview free
The catalog and the census free
The census and the gate free
Since your saved census
What the page flags
The readiness gate
The break-date catalog
Every integration, ranked
The notification rungs
Area by area
Your notice skeletons free
One notice per integration still on the old surface, with the payload the skill requires and the gaps you fill in - the request ID and the call count come from your logs.
Notices (Markdown)
The outreach plan metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved censuses
How it works - and what is sourced
The classification follows the skill. An integration is migrated when it made no call on the old surface for one full lookback after its first call on the replacement, or when its owner confirmed in writing that every job moved and no old call came later. The lookback is the longest business cycle you run on - a year-end close calls once a year - never a fixed 7 or 30 days. One replacement call proves nothing: a daily sync can move while a year-end job still calls the old route. Logs shorter than the lookback leave a row unknown, never migrated. A credential with no recent calls and no replacement call is dormant - seasonal or abandoned - and is never expired inside the sunset program.
Rows are bucketed by days to break against your escalation interval, then sorted by end customers affected (installs), never by call volume; a contract weight promotes a row into the top tier, and the top tier holds as many rows as your outreach hours allow. The readiness gate reads five lines: top tier migrated or excepted; the long tail notified at a verified contact or routed to the customer admin; unattributed calls zero on authenticated surfaces and under your floor on public ones; the replacement met its objective for at least two weeks with no open incident; every exception with an owner, a reason and an expiry. The verdict is go or no-go against those lines - never a share of calls.