[PR #585] fix: run jobs at interval instead of specific time #731

New Issue

OVERLORD · 2025-10-09T16:56:04+03:00

OVERLORD commented

2025-10-09 16:56:04 +03:00

Original Pull Request: https://github.com/pocket-id/pocket-id/pull/585

State: closed
Merged: Yes

While this is helpful for all jobs, it's particularly useful for the analytics job, to avoid all instances to send the ping at the exact same time, and to make sure it's always about 24 hours away.

Additionally, runs all database cleanup jobs in a single transaction, to avoid contention when all cleanup jobs are started at the same time (since they'd be competing to lock the database, especially with SQLite).

**Original Pull Request:** https://github.com/pocket-id/pocket-id/pull/585 **State:** closed **Merged:** Yes --- While this is helpful for all jobs, it's particularly useful for the analytics job, to avoid all instances to send the ping at the exact same time, and to make sure it's always about 24 hours away. Additionally, runs all database cleanup jobs in a single transaction, to avoid contention when all cleanup jobs are started at the same time (since they'd be competing to lock the database, especially with SQLite).

OVERLORD added the pull-request label 2025-10-09 16:56:04 +03:00

OVERLORD closed this issue

2025-10-09 16:56:05 +03:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-2#731