Quite large and growing auth.auth_requests table

Hi,
We have noticed very large and growing auth.auth_requests talbe, which is 28GB now and is growing, all other data for the zitadel databse is pretty small.
We are using Postgresql 15 in our case.
Is it supposed to be like this? Is there any safe way to clean/truncate it?

Ask Inkeep•12/10/25, 7:45 AM

Hi @RAleksejuk, 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/10/25, 7:45 AM

Answer

Yes, it's safe to delete old records from auth.auth_requestsauth.auth_requests. (1)

Based on a community discussion with ZITADEL team confirmation, you can safely delete records from auth.auth_requestsauth.auth_requests where the change_datechange_date is older than a certain period (e.g., 30-35 days) .

Example approach:

DELETE FROM auth.auth_requests WHERE change_date < NOW() - INTERVAL '35 days';

DELETE FROM auth.auth_requests WHERE change_date < NOW() - INTERVAL '35 days';

A user reported deleting records older than 35 days with no negative impact, and a ZITADEL team member confirmed this is safe.

Note: ZITADEL is working on better handling of scheduled background jobs which should automate maintenance tasks like this in a future release.

Ask Inkeep•12/10/25, 7:45 AM

To learn more, see the sources I considered:

[1] Is it possible to clean up irrelevant data in ZITADEL’s database?

Ask Inkeep•12/10/25, 7:45 AM

Feel free to tag @Ask Inkeep with additional questions.