Is there caching with token introspection?

I am receiving inconsistent results with the token introspection functions -- they don't update unless the respective user logs in and out again. I've opened a bug here: https://github.com/zitadel/zitadel/issues/11177

Does introspection use caching? I don't think it would, but if so, my understanding is that caching was an experimental feature.

GitHub

[Bug]:Token Introspection Not Updating Without Logging Out and In A...

Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment ZITADEL Cloud Version 2.71.10 Database PostgreSQL...

Ask Inkeep•12/11/25, 7:05 PM

Hi @nullsense, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•12/11/25, 7:05 PM

Answer

---

Based on the available sources, ZITADEL's introspection endpoint itself does not implement server-side caching. The introspection endpoint checks if the token is not revoked (by client or logout) and returns the current token status. (1)

However, caching on the client side is a recommended practice. A ZITADEL team member noted that clients can choose to cache introspection responses for a time that is acceptable for the application when session termination does not need to be instant—this is described as a "hybrid solution between not checking at all or on every request." (2)

Regarding the inconsistent results you're experiencing where changes don't reflect until the user logs in/out again—this behavior isn't documented as expected in the sources I have access to. The introspection endpoint should reflect the current state of the token.

Since you've already opened a GitHub issue (#11177) , that's the right approach. The team can investigate whether this is related to projections/views updating or another internal mechanism.

Ask Inkeep•12/11/25, 7:05 PM

To learn more, see the sources I considered:

[1] OpenID Connect Endpoints in ZITADEL
[2] JWT token validation: Centralized vs Decentralized

Ask Inkeep•12/11/25, 7:05 PM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] OpenID Connect Endpoints in...

Ask InkeepAPP•12/11/25, 7:05 PM

Got it. Tagging @Rajat for additional help.

Rajat•12/14/25, 8:48 AM

hey @nullsense thanks for your question, I don't think token introspection uses caching in zitadel. Rest, we will take a look at the issue next week. Thanks