Admin Tcc Recovery
TCC block→recovery funnel — the churn lever. Of machines that hit a Calendar/Contacts/Reminders permission wall in the window (a tool of that service returned permission_denied / tcc_* ), what happened next:
- recovered: every blocked service is now granted (effective state from outcomes)
- partial: some but not all blocked services granted
- stuck_active: still denied AND still active (last heartbeat <7d) → INTERVENTION TARGET
- churned_or_inactive: no heartbeat in 7d The stuck_machines list is who to nudge (active, blocked, recoverable).
get/admin/tcc-recovery
Request
- Base URL: https://api.local-mcp.com (the document declares no server; this is the origin it was published from)
- URL: https://api.local-mcp.com/admin/tcc-recovery
- Auth: none declared. Required headers: x-admin-key
Query parameters
daysinteger
Headers
x-admin-keystring required
Response
Successful Response
unknown required
Changes
No recorded changes to this operation across all 1 revision of this API.