Is Workato US Down Right Now? Discover if there is an ongoing service outage.

On October 7th, 2025, between approximately 03:15 AM and 03:49 AM UTC, the Workato platform experienced issues affecting Workato Genies. Customers may have experienced "Internal errors" when interacting with Genies. The issue has been resolved, and Workato Genies are now functioning normally. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

On October 6th, 2025, between approximately 03:20 AM and 04:02 AM UTC, the Workato platform experienced issues affecting Workato Genies. Customers may have experienced "Internal errors" when interacting with Genies or when attempting to stop them. The issue has been resolved, and Workato Genies are now functioning normally. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

We are aware that customers with incomplete recipes (no triggers specified) are experiencing HTTP 500 errors when calling the GET /api/recipes developer API endpoint. We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly. As a workaround, such recipes can be modified or removed if they are no longer necessary.

On September 29th, 2025, between approximately 03:27 AM and 04:27 AM UTC, the Workato platform experienced a degradation in the Event Streams API service. Clients utilizing the Event Streams API may have experienced 5xx errors when attempting to publish or consume from Event Stream topics. The issue has been resolved, and customers may retry failed API requests as needed. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

We’ve resolved a performance degradation that was causing errors on the Snowflake connector during long-running actions. Some customers may have experienced connection errors starting on September 10. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

We are currently investigating an issue affecting Workato's Excel connector. Customers may find that Excel connector actions fail with a 401 Unauthorized error. Customers may also observe that they are unable to establish or re-establish an Excel connection. We will provide additional information as soon as it is available.

We are investigating reports of increased latency when loading the Workato platform's UI. The Workato platform runtime and job processing are not affected. However, customers may experience network errors or timeouts when attempting to load the UI.

On September 1, 2025, between approximately 07:33 AM and 08:10 AM UTC, the Workato platform experienced a service degradation affecting job processing, the web interface, developer, and embedded API services. Customers may have observed job failures with "Internal Error" messages, job processing delays due to missing polls, errors in UI requests, and failures when starting recipes. Trigger events are still stored, and users may retry jobs if necessary. All services have been restored to normal operation. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

We have identified an issue with Genie skills and are working on a fix. Customers may observe Return response action failing with the error message "input validation errors". We will share additional information as soon as it is available.

On August 14, 2025, between approximately 05:00 and 10:04 UTC, Workato's Facebook connector experienced issues during job execution. Customers may have observed Facebook connector actions failing with 400 errors. The issue has been resolved, and customers may retry any failed jobs as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

We have identified the issue causing "Session timed out" errors in the Sage Intacct connector and are actively working to resolve it. We will share further updates as soon as possible.

On August 11, 2025, between approximately 01:15 PM and 01:48 PM PDT, Workato's QuickBooks Online connector experienced issues owing to the external service provider's API degradation. Customers may have observed errors in QuickBooks Online actions, while triggers may have experienced delays in job creation. Recipes with trigger errors may have been stopped after 60 consecutive errors and may require restarting. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance with this event.

On July 25, 2025, between approximately 9:06 PM and 9:07 PM UTC, Workato's Table Storage service experienced performance degradation. Customers may have observed jobs with Table Storage actions erroring out with the error message "Internal Error" or "Network Error". Customers using Table Storage triggers in their recipes may have experienced job creation delays. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

We are currently investigating an issue affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

On July 21, 2025, between 06:25:06 and 06:25:33 UTC, the Workato API platform experienced a brief service disruption. During this period, some requests may have failed with a 502 error. The issue has since been resolved. If you have any questions or require assistance regarding this event, please contact Workato Support (https://support.workato.com) or your assigned CSM.

On June 17, 2025, between approximately 10:30 AM and 10:32 AM UTC, the Workato platform experienced a degradation in its job processing infrastructure. Customers with polling triggers may have observed jobs being created only on a subsequent poll, as configured in the trigger. Job processing was delayed by several minutes, while certain jobs may have experienced failures with the message "Internal Error". Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

We are currently investigating an issue affecting role based access. Users may find Collaborator roles being reset to the out-of-box Operator or Analyst role. Customers using SAML along with SAML Role sync may disable Role sync and update collaborator roles manually. We will continue to share additional information as it becomes available.

Customers using Workato's Embedded Partner Platform APIs may be experiencing an increased rate of "429 Too Many Requests" errors. We have identified the issue and are working on a fix. We will share updates as soon as they are available.

On July 8th, 2025, between approximately 10:18 PM and 10:21 PM UTC, the Workato platform experienced degradation in job processing. During this time interval, customers may have observed job failures with internal errors. The issue has been resolved, and any jobs that failed during this interval may be repeated as required. Please contact Workato Support at https://support.workato.com or your assigned CSM if you have any questions or require assistance regarding this event.

On July 3, 2025, between approximately 02:57 AM - 03:02 AM UTC, the Workato API platform experienced a performance degradation. Customers may have observed APIM requests returning 503 or 401 errors. The issue has since been mitigated. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

On June 23, 2025, between approximately 6:22 PM to 7:34 PM PDT, the Workato platform experienced a performance degradation. Customers may have observed delays in job error email notifications, updates in the job status count and in the task count displayed on the dashboard. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

On June 23, 2025, between approximately 1:24 and 1:29 PM UTC, Workato FileStorage experienced a performance degradation. Customers using Workato FileStorage or actions that rely on the service, such as SQL Transformation, may have failed with the error message "Internal Error" or "An unexpected error has occurred", leading to job failures. Customers may repeat any failed jobs as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

The Workato platform experienced performance degradation between 3:17 PM and 3:20 PM UTC. Recipes with polling triggers may have experienced job creation delays. A job delayed by the performance degradation will be processed during the recipe's next configured poll without any intervention. The delay is subject to the poll interval selected in the trigger configuration. For recipes that use triggers from connectors apart from "Scheduler by Workato", customers may use the "Check for jobs now" button instead of waiting for the next poll.

On May 26, 2025, between approximately 06:34 AM and 06:56 AM PDT, the Workato platform experienced a degradation in its job processing service. Customers may have observed job failures, job processing delays, or timeout errors in the API Platform. Trigger events are still stored, and users may repeat a job if necessary. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

Workato's AssistIQ widget is currently unavailable due to an issue with our external service provider. We are continuing to monitor the issue and will provide updates as soon as they are available.

We have identified an issue affecting the NetSuite new/updated object batch trigger. As a result, some customers may encounter trigger errors in their recipes. Our team is actively working on remediation, and we will share further updates as soon as possible.

After further monitoring, this issue is now considered resolved. Customers should no longer experience any delays with webhook processing. If you continue to experience any issues, please contact Workato Support at support.workato.com

We have taken steps to remediate the performance degradation and are seeing improvement. We are continuing to monitor the issue.

We are currently investigating an issue affecting Workato's webhook gateway. Customers may experience delays processing webhook events. We will provide additional information as soon as it becomes available.

After further monitoring, this issue is now considered resolved. Customers should no longer experience any delays with webhook processing. If you continue to experience any issues, please contact Workato Support at support.workato.com

We have taken steps to remediate the performance degradation and are seeing improvement. We are continuing to monitor the issue.

We are currently investigating an issue affecting Workato's webhook gateway. Customers may experience delays processing webhook events. We will provide additional information as soon as it becomes available.

After further monitoring, this issue is considered resolved. Users should no longer encounter any issues in the Web UI. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has released a fix and is seeing improvement. We are continuing to monitor for any additional impact.

We are continuing to work on a fix for the issue and will share updates as soon as we have them.

We have identified the underlying cause of the issue and are working to remediate it. We will provide more updates shortly.

We are currently investigating an issue with viewing connections and folders in the Web UI. We do not believe any other components are affected by the issue. We will continue to share additional information as soon as it is available.

The issue has been resolved, and customers should no longer experience errors in Snowflake actions or triggers. Customers may restart any recipe that stopped due to 60 consecutive trigger errors, or repeat any failed jobs as required. Please contact Workato support at support.workato.com if you continue to experience any issues or have any questions about this event.

We have identified the underlying cause of the issue and are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an issue with Snowflake connections. Customers may be experiencing errors with Snowflake actions and triggers. We will share additional information as soon as it is available.

The issue with Workato's documentation has been resolved after a fix from our external service provider. Users may need to clear their browser cache and cookies for docs.workato.com. If you continue to experience issues, please contact Workato Support at support.workato.com.

We have identified an issue with our documentation (docs.workato.com). Customers may be unable to interact with certain page elements, such as the search bar. We are working with our external service provider to resolve the issue and will post additional information as soon as it is available.

After further monitoring, this incident is now considered resolved. Any jobs that failed due to an 'internal error' may be repeated as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

On April 6th, 2025, between approximately 3:39 AM and 3:41 AM UTC, the Workato platform experienced degradation in job processing. During this time interval, customers may have observed job failures with internal errors. The issue has been resolved, and the Workato platform has been restored to full functionality. Any jobs that failed during this incident may be repeated if required. Please contact Workato Support at https://support.workato.com or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this issue is now considered resolved. Customers may have experienced connections showing a "Connection Lost" message, leading to job failures. Affected connections may need to be re-established, and any failed jobs may be re-run as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the issue and is seeing improvement. We are continuing to monitor for any additional impact.

Users may experience Internal Server Errors with UI operations such as creating and deleting recipes or connections. Customers may experience job failures or delays in job creation. We are continuing to investigate and will provide additional information as soon as it is available.

We are currently investigating an issue affecting our encryption service. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Customers with affected AWS S3 connections should no longer experience "Connection Lost" errors in the UI, and jobs should now be processed as expected. Any failed jobs may be repeated as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to restore the affected connections. We are continuing to monitor the issue.

We are continuing to work on restoring affected connections. Customers may also reconnect their connection manually if required. Customers may repeat any failed jobs once the connection has been reconnected. We sincerely apologize for any inconvenience caused.

We have identified the issue that is causing errors in the Amazon S3 connector and are actively working to resolve it. Customers experiencing these errors may need to reconnect their Amazon S3 connections, even if the Connection page UI shows no issues. Customers may need to repeat the failed jobs once the connection has been reconnected. We sincerely apologize for any inconvenience caused.

Customers may experience job failures in recipes using the Amazon S3 connector. We are continuing to investigate and will provide additional information as soon as it is available.

We are currently investigating an incident affecting our Amazon S3 connector. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Database connector performance has been restored, and long-running database actions should now execute as expected. Any jobs that experienced performance degradation should be completed successfully. If you continue to experience any issues, please contact Workato Support at support.workato.com.

We have taken steps to remediate the issue and are seeing improvement. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the performance degradation and are working to take remediating steps.

We are currently investigating a performance degradation affecting database connectors, such as Microsoft SQL Server or Snowflake, using a cloud connection. Connections to databases using an OPA are not affected. Actions may take longer than normal to execute. We will continue to investigate and provide additional information as soon as it is available.

On March 7, 2025, between approximately 6:24AM and 7:19AM PST, Workato FileStorage experienced a performance degradation. Customers using actions that rely on Workato FileStorage, such as Workflow Apps or SQL Transformation, may have failed with the error message "Internal Error" or "An unexpected error has occurred", leading to job failures. APIM requests may have failed with 5xx errors. Customers may repeat any failed jobs as needed. If you continue to experience any issues, please contact Workato Support at support.workato.com.

The incident has been resolved. Customers with Automation HQ should now be able to use the environment switcher. Customers with connections using AWS IAM roles to authenticate with AWS services such as AWS S3 or AWS Lambda may have experienced jobs failing with the error message "Internal Error". Connections using AWS Secrets Manager may have experienced job failures with the error message "Couldn't find FederatedAccount without an ID". These errors may have been observed in both API Platform and non-API Platform recipes. Customers may also have observed delays in creating jobs with polling triggers, while jobs for recipes with real-time triggers may either be missing or delayed. Customers may also have experienced connections being disconnected after several errors. Customers may now repeat any failed jobs as required. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.

Customers may clear their cookies for app.workato.com to access the Workato platform but will continue to be unable to switch environments. We are continuing to investigate the issue.

The issue is affecting Automation HQ customers' ability to switch between environments. We are continuing to investigate.

We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Workato customers using webhooks in their recipes may have experienced delays in platform responses today between 03:25 PM and 04:00 PM UTC. Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

After further monitoring, the issue is now considered resolved. Customers should no longer experience trigger errors with recipes using Event Stream triggers. Recipes previously stopped due to 60 consecutive trigger errors may need to be cloned and restarted. If you continue to experience any issues or require further assistance, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the issue and is seeing improvement. Customers with recipes that use Event Streams triggers may be required to clone and restart their recipes if they have stopped after 60 consecutive trigger errors. We are continuing to monitor the issue.

We are continuing to investigate and will provide additional information as soon as it is available.

We are currently investigating an issue affecting Event Streams. Recipes with Event Streams' New Message trigger or New Batch of Messages trigger may be experiencing errors. We will provide additional information as soon as it becomes available.

After further monitoring, this issue is now considered resolved. Customers should be able to create and edit recipes on the Workato platform. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the issue. Customers should now be able to create new recipes and save changes to any existing recipes. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the issue and we are working to take remediating steps. Customers may be unable to create recipes or update existing ones. We will provide additional information as soon as it is available.

We are currently investigating an issue with the Workato platform UI. We will provide additional information as soon as it becomes available.

On January 24th, 2024, between approximately 09:09 AM and 09:34 PM PST, the Workato platform experienced a degradation in webhook processing. Customers may have observed delays in job processing for recipes that use real-time triggers, while recipes using Workbot for Slack triggers may have experienced an "Expired Trigger ID" error message in recipe actions. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this event.

On January 16th, 2024, between approximately 10:30 AM and 08:48 PM UTC, Workato's API Platform experienced a degradation in the API Proxy service. Customers may have observed API Proxy endpoints failing with 401 errors. Request failures were also not displayed in API Platform logs. The issue has been resolved, and customers may repeat API requests as needed. However, requests that failed during the incident will not be displayed retroactively in API Platform logs. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

On December 12th, 2024, Salesforce updated its domain URL format for several types of instances in both production and sandbox organizations. As a result, Salesforce connections in Workato may display a "Connection Lost" message, resulting in job processing failures or errors when building a recipe. Customers may be required to reconnect their Salesforce connection and update the "Organization/community custom domain URL" setting if used in the connection to reflect the updated domain URL for their Salesforce instance. Any failed jobs may be repeated as required and recipe builder functionality for Salesforce actions will be restored on reconnecting. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Some customers had experienced issues with the Workflow Apps feature, specifically with Data Tables. It was not possible to open Data Tables tab in Workato UI. Recipes relying on Data Table lines also experienced trigger delays. Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

On December 11th, 2024, between approximately 06:17 PM and 06:43 PM UTC, the Workato platform experienced a degradation in the Event Streams service. Customers may have observed Event Streams publish actions failing with an error message of "An unexpected error has occurred," leading to job failures. Recipes with an Event Streams trigger may have experienced delays in triggering new jobs, while API recipe endpoints using Event Stream actions may have responded with a 500 status code. Clients utilizing the Event Streams API may have experienced 5xx errors when attempting to publish or consume from Event Stream topics. The issue has been resolved, and customers may repeat failed jobs or API requests as needed. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

This incident has been resolved.

We are seeing improvements and will continue to monitor the issue.

We are currently monitoring an incident with the Salesforce API (https://status.salesforce.com/generalmessages/1476) that is causing failures in job creation from Salesforce platform events. We will provide additional information as soon as it becomes available.

Our service provider has notified us that their service has been restored. Customers should now be able to open chats with Workato Support. Please submit a ticket if you continue to experience issues at https://support.workato.com.

Workato customers may experience issues when interacting with Workato Chat Support. We are currently awaiting updates from our service provider. For urgent issues, please submit a ticket to Workato Support at https://support.workato.com.

On October 29th, 2024, between approximately 06:49 AM and 07:57 AM PDT, the Workato platform experienced a degradation in its job processing service. Customers may have observed database connector actions failing with an error message of "Internal Error," leading to job failures. The issue has been resolved and customers may repeat failed jobs as required. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this incident is now considered resolved. Webhook processing latency has returned to normal, and customers should no longer experience any delays in processing webhook events. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

On October 17, 2024, between approximately 07:14 AM and 07:30 AM PDT, the Workato platform experienced a degradation in its job processing service. Customers may have observed job failures with the error message "Internal Error." Due to the nature of the failure, the job details page for a failed job will display the message "No data to show." Trigger events are still stored, and users may repeat a job if necessary. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Workato customers may experience issues when sending messages through our external chat service. We are currently investigating the cause.

On October 3, 2024, between approximately 07:02 AM and 07:10 AM (UTC), the Workato platform experienced an issue with its data encryption service. Customers may have observed job failures with the error message "Internal Error." Due to the nature of the failure, inspecting job details will also not display job failure details and will display the message "No data to show." We can confirm that failed jobs can be repeated. In addition, recipes may have experienced delays in creating jobs. They would instead have generated a job upon receiving the next trigger event, depending on the trigger type and its configuration. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We are investigating an incident affecting our HTTP connector. Customers might experience "extraneous characters found in request URL" errors when using HTTP send request actions. We will provide additional information as soon as it becomes available.

On September 9, 2024, at approximately 12:45 PM (UTC), the Logging Service used by Embedded customers in the Logger by Workato Connector experienced a service degradation. This issue resulted in logs generated by the Logger by Workato step in recipe jobs not being sent to the Workato Logging Service when the "Send to Workato log service" toggle was enabled. The issue was resolved on September 11, 2024, at approximately 10:15 AM (UTC). The Logging Service is now fully operational, and logs are being sent to the Workato Logging Service as expected. At Workato, the performance and reliability of our platform and service are our top priorities, and we apologize for any inconvenience this may have caused. Please contact Support or your assigned CSM if you have any questions or require assistance regarding this incident.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the incident and are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an incident affecting webhook processing. Customers may observe delays in job creation in recipes with real-time triggers. We will provide additional information as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Customers should now be able to load pages on app.workato.com without any issues.

We are continuing to investigate the issue affecting the loading of pages on app.workato.com. At this time, our system appears to be healthy and we do not see any issues on our end. The issue may be related to a set of ISPs in the Asia region. We recommend that you check with your ISP to determine if there are any issues on their end. We will provide additional information as soon as it becomes available.

We are currently investigating an issue affecting the loading of pages on app.workato.com. We will provide additional information as soon as it becomes available.

Support chat is back online and the incident is now considered resolved. The Workato platform has been restored to full functionality. If you continue to experience any issues, please use our Support Portal (https://support.workato.com/en/support/home) to submit a ticket.

We are experiencing an issue with our third-party chat service, which is being investigated by the service provider. Users may experience their browser tab becoming unresponsive. If you have an urgent concern, please use our Support Portal (https://support.workato.com/en/support/home) to submit a ticket.

This incident has been resolved.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We are currently investigating an incident affecting the Workato API Platform. Customers might experience failures in processing API Platform requests. We will provide additional information as soon as it becomes available.

We are aware of the Microsoft Windows and Crowdstrike issues and related outages. Workato and the Workato platform are not impacted. However, customer recipes related to Microsoft applications, third-party services directly affected by the outage, or MS Team Workbot may have been impacted. If you have any questions or need technical assistance, please contact your Customer Success Manager or reach out to our Support team at https://support.workato.com Detailed information on Microsoft Windows and Crowdstrike issues and related outages: - https://www.crowdstrike.com/blog/statement-on-falcon-content-update-for-windows-hosts/ - https://azure.status.microsoft/en-us/status

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. We have encountered a domain resolution issue with https://www.workato.com, impacting the Workato API, Workbots, and the configuration of new connections that depend on callbacks using endpoints associated with this domain. If you continue to experience any issues, please contact Workato Support at support.workato.com

We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an issue affecting Embedded Customers not able to load embedded Workato instances

Our team has taken remediating steps, and this incident is now considered resolved. Recipes using the Gmail connector should no longer throw any authorization errors, while recipes using GMail triggers can now be restarted. However, customers who continue to experience connection issues may need to reconnect their GMail connections. If you continue to experience any issues, please contact Workato Support at support.workato.com.

We are continuing to work on a fix for this issue.

We have identified the underlying cause of the issue affecting our Gmail connector and are working to take remediating steps. Recipes using Gmail triggers will have stopped after 60 consecutive trigger errors and recipes with Gmail connector actions will continue to throw authorization errors. We will provide more updates shortly.

After further monitoring, this incident is now considered resolved. Customers should now be able to search for recipes in the Community Library. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has identified the issue and has taken steps to remediate the incident. We are seeing improvement and are continuing to monitor for any additional impact.

We are currently investigating an issue where users may be unable to search for recipes in the Community Library. We will provide additional information as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Customers should now be able to use the Javascript connector and run jobs successfully. Customers may rerun any failed jobs or take other appropriate remediation steps as required. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor the issue.

We are continuing to investigate the issue and will provide additional information as soon as it is available.

We are investigating an issue affecting the Javascript connector. Customers using the connector may observe job failures. We will provide additional information as soon as it is available.

After further monitoring, this incident is now considered resolved. Customers should now be able to connect to SAP Concur's SFTP instance and run jobs successfully. Failed jobs may be rerun as required, and any recipes with the SFTP trigger that stopped due to trigger errors must be restarted. If you continue to experience any issues, please contact Workato Support at support.workato.com.

SAP Concur has reverted the change, and customers should now be able to connect to the SAP Concur SFTP server successfully. We are continuing to monitor for any additional impact.

We are continuing to work on a resolution for the SFTP connection issue. We will provide additional information as soon as it is available.

We are currently working to resolve an issue affecting our customers who are connecting to SAP Concur SFTP servers. These customers are experiencing SFTP connection issues due to SAP Concur's latest security release, introduced yesterday. The SAP Concur release affected an additional part of server communication and changed the host key verification algorithms. Since the release, only two types of algorithms continue to be supported by SAP Concur SFTP servers, and none are currently supported by Workato. This change was not anticipated by Workato since the official AWS docs state that up to 6 algorithms are supported. https://docs.aws.amazon.com/transfer/latest/userguide/security-policies.html#security-policy-transfer-2022-03. We will provide additional information as soon as it becomes available.

After further monitoring, this incident is now considered resolved. The Email by Workato connector is delivering emails as expected and has cleared the backlog of undelivered emails. Customers may have observed that emails sent from the Workato domain, such as error notifications, team invitations, and password reset emails, were delayed or sent out of order. If you continue to experience any mail delivery issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We are currently investigating an issue affecting the delivery of emails sent by the Email by Workato connector. We will provide additional information as soon as it becomes available.

Certain customers on the Workato platform may have experienced job failures between 10:03 UTC and 15:00 UTC due to an issue with an internal database. A small number of jobs may have failed with an error message of "Internal Error," and the job details page for the failed job will display "No data to show" regardless of the workspace's configured data retention period. Customers may be able to repeat any failed jobs but are advised to inspect any connected applications for changes as jobs may have been partially executed and take appropriate corrective measures. We apologize for any inconvenience caused and are taking remediation steps to prevent this issue in the future. Please contact Workato Support at support.workato.com or your assigned CSM if you require further assistance.

After further monitoring, this incident is now considered resolved. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We will provide additional information as soon as it is available.

We are continuing to investigate the issue and will provide additional information as soon as it is available.

We are continuing to investigate the issue and will provide additional information as soon as it is available.

We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.

After further monitoring, this incident is now considered resolved. Customers should now be able to access the Workato FileStorage UI. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to restore access to the UI and is seeing improvement. We are continuing to monitor for any additional impact.

We are currently investigating an issue affecting the Workato FileStorage UI. Recipes using Workato FileStorage will continue to process jobs normally and are not affected. We will provide additional information as soon as it becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue that is causing connection errors with the SFTP connector and are working to take remediating steps. We will provide additional information as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Recipe steps that use in-memory lookup table formulas should now return the correct results. Customers may need to rerun earlier jobs or take other remediating actions if required as the formula itself did not throw errors during the incident. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has released a fix to remediate the issue and is seeing improvement. We are continuing to monitor for any additional impact.

Customers may have observed recipe steps using in-memory lookup table formulas return null instead of the expected value. This may have led to runtime errors. We have identified the underlying cause of the issue and are investigating a fix. We will post additional information as soon as it is available.

Between 8:41 AM PST and 8:45 AM PST, customers with recipes using the Add Rows or Add Batch of Rows action in the Lookup Tables by Workato connector may have experienced job failures with the error message Internal Error. Customers are requested to repeat any failed jobs that may have occurred during this timeframe. For further assistance, please contact Workato support at support.workato.com.

This incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com

We have identified the incident's underlying cause and are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an issue affecting our Platform. We will provide additional information as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Slash commands in Workbot for Slack are now working correctly. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.

We are currently investigating an incident affecting our platform. Customers might experience an elevated number of dispatch_failed errors using Workbot for Slack. We will provide additional information on all affected components as soon as it becomes available.

After further monitoring, this incident is now considered resolved. Customers should now be able to start and stop their recipes. If you continue to experience any issues, please contact Workato Support at support.workato.com.

Our team has taken steps to remediate the issue and is seeing improvement. We are continuing to monitor for any additional impact.

We are currently investigating an issue affecting the starting and stopping of recipes. We will provide additional information as soon as it becomes available.