Previous incidents

The root cause was database connection pool exhaustion triggered by a sudden increase in concurrent requests to the Mobile and Web API services.
The devops team scaled up the database connections to handle the increased load. System performance stabilized after the scale-up completed. Continuous monitoring was enabled to validate stability.
Actions Taken:
Short-term
- Verified successful scale-up and confirmed service recovery.
- Enabled real-time monitoring on database connection utilization...

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.