https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36702

--- Comment #28 from Michaela Sieber <[email protected]> ---
Thanks Kyle!

We were a bit surprised because we expected the time interval between retries
to remain constant as defined in syspref BackgroundJobsRetryDelay.
However, that is not the case—the time gap between successive retries keeps
increasing.
For example, with 5 retries and an interval of 10, the timing looks like this:


+----+--------+---------------------+---------------------+----------+-------------+---------+-----------------+---------------------+
 
| id | status | enqueued_on | started_on | ended_on | max_retries | retries |
previous_job_id | not_before |
+----+--------+---------------------+---------------------+----------+-------------+---------+-----------------+---------------------+
| 12 | failed | 2026-07-03 09:39:28 | 2026-07-03 09:39:34 | NULL | 5 | 0 | NULL
| NULL |
| 13 | failed | 2026-07-03 09:39:34 | 2026-07-03 09:39:35 | NULL | 5 | 1 | 12 |
2026-07-03 09:39:34 | -> 1. retry: 0 secs
| 14 | failed | 2026-07-03 09:39:35 | 2026-07-03 09:39:45 | NULL | 5 | 2 | 13 |
2026-07-03 09:39:45 | -> 2. retry: 10 secs
| 15 | failed | 2026-07-03 09:39:45 | 2026-07-03 09:40:05 | NULL | 5 | 3 | 14 |
2026-07-03 09:40:05 | -> 3. retry: 20 secs
| 16 | failed | 2026-07-03 09:40:06 | 2026-07-03 09:40:36 | NULL | 5 | 4 | 15 |
2026-07-03 09:40:36 | -> 4. retry: 30 secs
| 17 | failed | 2026-07-03 09:40:36 | 2026-07-03 09:41:17 | NULL | 5 | 5 | 16 |
2026-07-03 09:41:16 | -> 5. retry: 40 secs


In addition to the test plan, we also verified whether ERM havesting jobs are
retried. This was not the case, as described in comment 8 of the test plan.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to