This is an overflow of the 32-bit long timeSetEvent uDelay parameter.
Even though you set the uDelay parameter in milliseconds, internally in the function, it uses 100 nanosecond units. So a value of 429,496 ms (4,294,960,000 = 0xFFFFE380) is the maximum. This is about 7 minutes and 9 seconds. If you set uDelay to 429,497 the event will almost immediately occur.
If we examine these values in hexadecimal, we see: �
429,496(ms) * 10,000 = 4,294,960,000 (100ns) = 0xFFFFE380
429,497(ms) * 10,000 = 4,294,970,000 (100ns) = 0x00000a90
The second value goes beyond the limit and the hexadecimal value starts to count over again.
This problem happens only when using TIME_PERIODIC mode.