[BUG]: when clock breaks and doesn't crash, clock actions are missed since the crash

[doctorpangloss]

Describe the bug
Let's say clock breaks (it doesn't crash #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:

1. Break clock
2. An invoicing date passes.
3. Observe the invoice isn't sent. This is expected.
4. Unbreak clock
5. Observe the invoice still isn't sent.
   Expected behavior
   If clock breaks, it should send the invoices it missed.
   Screenshots

Support

• Version. 1.2.1

[jdenquin]

If your clock restart during the same day, you invoice should be processed, if the date change, you have to manually run a billing process for the date you missed.

[jdenquin]

@doctorpangloss we work on a Troubleshooting section in our documentation to understand and fixe those cases, will keep you posted asap!