Summary:
The issue occurs when events are submitted with timestamps older than the allowed time window. In this case, cached events from several months prior were sent when a player returned, and their timestamps fell outside Unity’s three‑month acceptance period. The resolution involves identifying and preventing submission of stale, cached events with outdated timestamps.
Symptoms:
- Error message: “Event timestamp outside valid boundaries”
- Issue appears when players return after a long absence and cached events are sent.
Cause:
Events were cached on the client some months earlier and only sent when the player logged back in. These events had timestamps older than the permitted window. Unity’s backend does not accept events with timestamps older than three months, causing them to be rejected with the “Event timestamp outside valid boundaries” error.
Resolution:
- Review client logic for caching and resending events to ensure events are not stored for more than three months.
- Implement checks to discard or adjust stale events whose timestamps fall outside the three‑month acceptance window before submission.
- Investigate whether any devices have incorrect system time settings that could result in invalid timestamps being recorded.
- After updating the client logic, monitor production logs to confirm that no further events are rejected for invalid timestamps.