kshitij
cc245e84d2
fix: correct cron mid-run restart claim in salvaged docs
...
The original PR #78453 said 'A job that was mid-run during a restart
resumes according to the attempt policy described in this page.' This
is misleading — the existing docs explicitly state 'Unknown attempts
are audit records and are never automatically rerun.' Corrected to
accurately describe: the mid-run attempt is marked unknown (not retried),
but the job's next scheduled tick fires normally.
2026-08-05 21:33:44 +05:30
..
2026-08-01 21:17:51 -04:00
2026-07-29 08:48:05 -07:00
2026-07-12 00:26:49 -07:00
2026-07-18 10:07:46 -07:00
2026-07-29 08:48:05 -07:00
2026-07-29 08:48:05 -07:00
2026-07-17 13:44:12 -07:00
2026-07-29 12:19:37 -07:00
2026-07-29 08:48:05 -07:00
2026-07-29 09:44:59 -07:00
2026-08-05 21:33:44 +05:30
2026-07-29 09:45:11 -07:00
2026-08-05 14:00:25 +05:30
2026-07-29 08:48:05 -07:00
2026-07-29 08:48:05 -07:00
2026-08-03 19:02:12 +05:30
2026-08-05 21:33:44 +05:30
2026-06-15 21:34:09 +00:00
2026-08-02 15:01:11 -07:00
2026-08-03 22:53:32 +05:30
2026-07-29 08:48:05 -07:00
2026-06-21 17:06:48 -07:00
2026-08-05 21:33:44 +05:30
2026-07-29 17:11:30 +05:30
2026-08-05 21:33:44 +05:30
2026-07-29 08:48:05 -07:00
2026-08-05 21:33:44 +05:30
2026-07-23 21:07:18 -07:00
2026-07-28 07:58:01 -07:00
2026-08-03 12:29:49 -07:00
2026-07-29 08:48:05 -07:00
2026-07-06 12:11:31 -07:00
2026-07-10 13:10:45 +05:30
2026-07-29 08:48:05 -07:00
2026-07-29 08:48:05 -07:00
2026-06-20 23:23:47 -07:00
2026-06-04 01:19:28 +05:30
2026-06-07 01:39:06 -07:00
2026-08-03 19:11:30 +05:30
2026-07-29 19:48:37 -07:00
2026-07-29 08:48:05 -07:00
2026-05-28 02:41:36 -07:00
2026-07-29 10:08:53 -07:00
2026-07-29 14:04:21 -06:00
2026-07-29 08:48:05 -07:00
2026-07-29 08:48:05 -07:00
2026-07-23 21:06:47 -07:00