store.sqlite3 size

[francescolovecchio]

Hi,
I noticed that for some sessions the file store.sqlite3 is big.
Is there any param in order to set up a retention like 2 weeks for the messages in order to shrink / keep small the database?

I noticed that many request to /api/session/chats/overview?limit=10&merge=true are going in timeout, I don't know if this is related.

Regards

[cookesan]

I do not see a retention-period setting for store.sqlite3.

The knobs that affect growth are at the storage/sync level. For NOWEB, the session store can be enabled/disabled and fullSync controls whether contacts/chats/messages are pulled broadly. For GOWS, storage.messages=false disables local message storage. Once the DB is already large, changing those settings will not automatically compact the existing SQLite file.

For the timeout side, avoid asking for huge overviews/messages in one request. The API has paged/limited message reads, and the chats overview also has a POST path for narrowing by IDs. If you need to reclaim disk from an existing file, back it up first and use the project's delete/clear endpoints or recreate the store; manual SQLite edits are easy to make inconsistent.

[francescolovecchio]

Thank you, fullSync is already disabled and the session store must be enabled in order to get messages from api.
For the timeout side, it is from the default dashboard and the limit is 10, so I think this is not huge overviews/messages in one request. I don't see any endpoint in order to clear the session without delete it and the best would be to delete info older than X days, not all