Immutable solution version
Clerk event: session.revoked is a forced logout, treat it as a security event
Complete solution
session.revoked means authority ended the session, not the user. Invalidate everything derived from that session and check whether the revoke was yours or a surprise.
session.revoked: forced logout
Fires when a session is revoked through the Dashboard, the Backend API, or an automated security action. The user did not choose this.
What to do on receipt
- Read
evt.data.id(session id) andevt.data.user_id. Mark the session revoked in your records immediately. - Invalidate everything you derived from that session: cached role checks, issued API tokens, device trust flags, "keep me signed in" state. A revoked session must not keep working through your caches.
- Determine the source. If your own code or admin called revoke, this is the expected echo; log it and stop. If you did not initiate it, treat it as a security review trigger: check the user's recent activity for compromise signs.
- Notify the user on their remaining sessions or by email ONLY if the revoke was a surprise. "You were signed out of a device by an admin" is useful. Noise about your own routine revokes trains users to ignore the real alerts.
- Return 200.
The trap
Caching past the revocation. The classic failure is a permissions cache keyed by user id with a long TTL: the session dies in Clerk but your app keeps honoring the old grants for an hour. Revocation must punch through every cache layer.
Checklist
- Your revoke call and the webhook echo race. Make revocation idempotent so the echo is a no-op, not an error.
- Distinguish this from
session.ended. A sign-out needs no review; a revoke might. - If you run step-up or re-authentication flows, a revoked session should force full re-authentication, not a silent refresh.
Evidence
Clerk's event catalog (Dashboard → Webhooks → Event Catalog) lists session.revoked as a distinct session event. The verifyWebhook reference documents the evt payload shape used to read session and user ids. Verified live at https://clerk.com/docs/reference/backend/verify-webhook.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_zVh8McBm6xeCyhYA0R9VoA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk event: session.revoked is a forced logout, treat it as a security event <span>— Vectle</span></a>