Sorry for the delay on this. Having looked into it, the problem happened because the check that limited the number of applicable events would only check events from <current time> - 259200. In contrast, the paycheck events were applied retroactively.
For example: let's say the user's historical records started at 1670540400 (Thursday, 8 December 2022 23:00:00). The limiter that was supposed to skip the subsequent 3 events (what your settings show, you need to change your limit to 172800 if you want it to apply every 3rd day), would check for events starting at 1678980178 - the exact real-time second the transaction was being inserted.
For every event other than the four daily events (Daily, Interest, Taxation, Paycheck) this was not a problem, since the transaction's date would always match the exact real-time second the transaction was being inserted.
Those four events, however, work based on inserting as if they happened at midnight. Therefore, especially for the three events that support catch-up (Interest, Taxation, Paycheck), the check would never flag events as having been inserted.
