Workato Outage History

Workato's Audit Log Streaming Service experienced degradation for 3.3 hours, causing delays in audit log replication with log entries taking longer than expected to be delivered to customers. The team identified the root cause and implemented remediation steps to resolve the issue. The service has been restored to normal operation, with affected events being delivered over the following week.

Workato experienced a 2.1-hour incident affecting Deployments, Recipe Lifecycle Management (RLCM), and the Developer API MCP, causing customers to encounter "No such file or directory" errors when attempting to deploy recipes, RLCM manifests, or use Developer API MCP tools. The issue was resolved after deploying a fix and monitoring the platform recovery, with customers able to retry any previously failed operations.

Workato's Genie Conversation service experienced degradation for 9 minutes, causing conversation pages to not display new chat events and preventing Genie test mode from functioning properly. The issue affected some customers' ability to see real-time chat updates and test Genie functionality. The service was restored after active remediation efforts by the Workato team.

Workato experienced a 12.1-hour service disruption starting May 8, 2026 at 1:59 AM UTC, caused by an incident with their AWS cloud infrastructure provider. Customers encountered 500 errors when calling API Platform endpoints, recipe job failures, and unresponsive Workbot services for Slack and Teams. The issue was resolved after monitoring and working through the underlying AWS infrastructure problems.

Workato Go experienced a 3.2-hour service disruption caused by an AWS incident that prevented users from accessing the application and affected knowledge base creation and retrieval capabilities. The outage completely blocked access to Workato Go and rendered knowledge base ingestion services non-functional. Service was fully restored with all capabilities functioning normally after the underlying AWS issue was resolved.

Workato users experienced a server error that prevented them from accessing the Conversations page for 3.3 hours. The engineering team identified the underlying cause and implemented a fix. The issue was resolved and users can now access the Conversations page normally.

Workato's Salesforce connector experienced an issue for 5.2 hours where customers encountered Internal Errors when using the upload action. The problem affected Salesforce data upload operations, causing job failures for users attempting to transfer data through the connector. The issue was resolved through remediation steps, and customers were advised to retry any failed jobs.

Workato experienced an issue where updating projects (such as renaming) inadvertently converted them into Workflow App projects, with affected customers seeing "Workflow App project was created" entries in their Activity Logs. The incident affected the website component for 8.7 hours, though no data loss or disruption to existing recipes or jobs occurred. A fix was deployed to prevent further conversions, and Workato resolved the incident while continuing to revert affected projects to their original state over the following working days.

Workato experienced a major incident affecting database connectors, causing actions and triggers to fail with "502 Bad Gateway" errors. The issue impacted customers' database connector functionality for 2.2 hours. The problem was resolved through remediation steps, and customers were advised to retry any failed jobs as needed.

Workato's "Message template by Workato" connector experienced a major outage for 3.1 hours, causing customers to encounter internal errors when using actions. The underlying cause was identified and remediation steps were implemented, with the platform showing improvement during monitoring. The issue was fully resolved, allowing customers to retry any failed jobs as needed.