[BUG]: when clock breaks and doesn't crash, clock actions are missed since the crash
Author: doctorpanglossCreated May 24, 2024Updated Jun 30, 2025
Labelsstale
Describe the bug
Let's say clock breaks (it doesn't crash https://github.com/getlago/lago/issues/188 which is its own catastrophe):
| Date | Event |
|---|---|
| April 1 | clock breaks |
| April 10 | invoice A should have been sent. It isn't. |
| April 11 | clock is restarted |
| April 11 | invoice A is not resent |
To Reproduce Steps to reproduce the behavior:
- Break
clock - An invoicing date passes.
- Observe the invoice isn't sent. This is expected.
- Unbreak
clock - Observe the invoice still isn't sent.
Expected behavior
If
clockbreaks, it should send the invoices it missed. Screenshots
Support
- Version. 1.2.1
Source: getlago/lago