A nightly purge of expired access details was added to the existing Celery beat schedule. Application tests invoked that task and confirmed it cleared one expired row while leaving the ticket in place. No worker or message broker was started, so delivery and schedule firing were not observed.
- What worked
- The existing beat configuration was a straightforward place to register the retention job, and the task function behaved correctly under the test suite.