Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Robocorp and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Robocorp.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
API | Active |
Robots | Active |
View the latest incidents for Robocorp and check for official updates:
Description: We encountered errors with the Slack integration in Control Room this week on Wednesday 19th and Thursday 20th. Customers impacted by failures to deliver Slack notifications have been explicitly contacted along with details of the notifications that were not delivered successfully. The situation has been restored back to normal.
Status: Resolved
Impact: None | Started At: Oct. 21, 2022, 9:02 p.m.
Description: We encountered errors with the Slack integration in Control Room this week on Wednesday 19th and Thursday 20th. Customers impacted by failures to deliver Slack notifications have been explicitly contacted along with details of the notifications that were not delivered successfully. The situation has been restored back to normal.
Status: Resolved
Impact: None | Started At: Oct. 21, 2022, 9:02 p.m.
Description: We have fixed an issue causing Control Room scheduler to incorrectly start multiple runs for a subset of scheduled runs between Oct 19 16:15 EEST (6.15am PT) and Oct 20 10:20 EEST (1.20am PT). The root cause of the issue was an insufficient timeout configuration, which in some cases caused our resiliency mechanism to trigger a retry before the processing of the original request had been completed. We apologize for any inconvenience.
Status: Resolved
Impact: None | Started At: Oct. 20, 2022, 7:30 a.m.
Description: We have fixed an issue causing Control Room scheduler to incorrectly start multiple runs for a subset of scheduled runs between Oct 19 16:15 EEST (6.15am PT) and Oct 20 10:20 EEST (1.20am PT). The root cause of the issue was an insufficient timeout configuration, which in some cases caused our resiliency mechanism to trigger a retry before the processing of the original request had been completed. We apologize for any inconvenience.
Status: Resolved
Impact: None | Started At: Oct. 20, 2022, 7:30 a.m.
Description: Bulk of the errors was caused by a change that caused misreporting of 4xx status codes as 5xx. This was visible to clients of the process API, but impacted only requests that failed regardless. Additionally, between 11:49 and 12:05 EEST a subset of requests were failing. We will notify all impacted paid tier customers explicitly during today.
Status: Resolved
Impact: Major | Started At: Sept. 13, 2022, 9:01 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.