Actor cache TTL — fetched_at stored but never checked for staleness #3

Closed
opened 2026-05-29 10:22:11 +00:00 by GKaszewski · 0 comments
Owner

ap_remote_actors.fetched_at is persisted on every actor fetch but no code path checks it for staleness. Long-lived cached actors will serve stale keys/endpoints indefinitely.

Suggested fix: add a configurable TTL (e.g. 24h default). On actor dereference, if fetched_at + ttl < now, re-fetch from origin and update the row.

`ap_remote_actors.fetched_at` is persisted on every actor fetch but no code path checks it for staleness. Long-lived cached actors will serve stale keys/endpoints indefinitely. Suggested fix: add a configurable TTL (e.g. 24h default). On actor dereference, if `fetched_at + ttl < now`, re-fetch from origin and update the row.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GKaszewski/k-ap#3