The issue was resolved on Oct 8, 2025, at 9:56 AM.
The Mobile API environment experienced intermittent timeouts and failures in displaying the Remote Clock-in card. Investigation revealed that the issue occurred during autoscaling, when new backend instances were being provisioned. Due to memory and storage limitations, these instances required a brief warm-up period, during which some requests were temporarily dropped for approximately two minutes.