Background job run log
Every run of every declared job, newest first — standing-order execution, simulated batch settlement and returns, and the period-limit reset. The counts on each row are the ones that job defines, so “executed”, “settled” and “rolled over” keep their own meanings. For each job's schedule, queue and manual trigger, see the jobs dashboard.
Not polling: nothing on screen can change status any more. Showing state as of .
Showing 29 of 29 recorded runs.
| Started (UTC) | Job | Trigger | Status | Duration | Counts | Outcome |
|---|---|---|---|---|---|---|
| 2026-08-19 06:20:59 UTCslot 2026-08-19 06:20:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 06:15:48 UTCslot 2026-08-19 06:15:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 06:10:57 UTCslot 2026-08-19 06:10:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 06:05:48 UTCslot 2026-08-19 06:05:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 5 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 06:00:55 UTCslot 2026-08-19 06:00:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:55:48 UTCslot 2026-08-19 05:55:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 5 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:50:53 UTCslot 2026-08-19 05:50:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:45:48 UTCslot 2026-08-19 05:45:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:40:51 UTCslot 2026-08-19 05:40:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:35:48 UTCslot 2026-08-19 05:35:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:30:48 UTCslot 2026-08-19 05:30:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:25:47 UTCslot 2026-08-19 05:25:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 8 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:20:45 UTCslot 2026-08-19 05:20:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:15:44 UTCslot 2026-08-19 05:15:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:10:43 UTCslot 2026-08-19 05:10:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:05:41 UTCslot 2026-08-19 05:05:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 05:00:40 UTCslot 2026-08-19 05:00:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 10 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:55:39 UTCslot 2026-08-19 04:55:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:50:37 UTCslot 2026-08-19 04:50:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:45:36 UTCslot 2026-08-19 04:45:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 6 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:40:34 UTCslot 2026-08-19 04:40:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:35:33 UTCslot 2026-08-19 04:35:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:30:32 UTCslot 2026-08-19 04:30:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:25:30 UTCslot 2026-08-19 04:25:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:20:29 UTCslot 2026-08-19 04:20:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:15:28 UTCslot 2026-08-19 04:15:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 8 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:10:04 UTCslot 2026-08-19 04:10:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:06:23 UTCslot 2026-08-19 04:05:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 8 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
| 2026-08-19 04:00:45 UTCslot 2026-08-19 04:00:00 UTC · attempt 1 | Period-limit resetperiod-limit-reset | platform schedule | succeeded | 7 ms | 0 examined · 0 rolled over · 0 merged · 0 skippedUSD 0.00 carried to history | No customer's daily or monthly period had ended, so no limit counter was reset. Every live period keeps the spend already booked against it. |
Sample book disclosure: the customer accounts, staff users and sanctions watchlist in this environment are seeded demonstration data created by this module — there is no connection to a real core banking system, payment scheme or sanctions feed. Batch (ACH-style) clearing and high-value wire settlement both run through this module's own SIMULATED settlement engine, never a real scheme or wire network.