Incidentsby GlyphAutomate is facing issues
Jul 7, 12:47 UTCJul 7, 19:00 UTC
Duration
6h 13m
Impact
Critical
Root cause
Config change
BrowserStack, 90 days
36 incidents
Affected
Automate
Final update
Between 12:47 and 19:00 UTC, a subset of users running test sessions on Chrome 149 and 150 experienced an elevated rate of idle timeouts. This was caused by an configuration change, which has since been identified and rolled back. The issue is now fully resolved, and sessions on Chrome 149/150 are operating normally.
Timeline
- Resolved · Jul 7, 19:00 UTC
Between 12:47 and 19:00 UTC, a subset of users running test sessions on Chrome 149 and 150 experienced an elevated rate of idle timeouts. This was caused by an configuration change, which has since been identified and rolled back. The issue is now fully resolved, and sessions on Chrome 149/150 are operating normally.
- Investigating · Jul 7, 12:47 UTC
We are currently investigating this issue.
More from BrowserStack
Full historyLow Code Automation - Builds is facing issueslasted 1mLow Code Automation - Builds is facing issueslasted 1mSpectra (Accessibility Rule Engine) is facing issueslasted 0mAccessibility DevTools is facing issueslasted 0mAutomate is facing issueslasted 10mLow Code Automation - Builds is facing issueslasted 1m