Is Tray.ai Down Right Now? Check if there is a current outage ongoing.

Beginning at 18:11 GMT, users may have begun experiencing issues with the Gmail trigger. We are currently investigating the source and will continue to update here. We apologize for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

We have recognized failures on on-prem connectors in the EU environment. We are investigating the cause and will work towards resolution. Please reach out to support if you have any questions or concerns about this incident.

We encountered an error with on-prem connector executions at 14:31 GMT. Customers using on-prem connections may have noticed a disruption in executions for those connectors. Our engineering teams have applied a fix and are currently monitoring the results. We apologize for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

The scheduled maintenance has been completed.

Verification is currently underway for the maintenance items.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

On Tuesday, 27th May 2025, we will be updating our log-streaming product. The maintenance window is scheduled to start at 09:00 BST (01:00 PDT, 18:00 AEST).No interruption or change in service is expected, but you may experience small fluctuations in the rate and size of requests received by the endpoint used in your log streaming setups.If you have any questions, or would like to get in touch about anything at all, please drop us a line at support@tray.ai.

Our engineers have identified and resolved an issue that affected a small subset of connectors, leading to degraded performance between 19:15 and 21:56 GMT (12:15 to 14:56 PDT). During this time, some workflows using these connectors may have failed. The issue has now been fully resolved, and all services are operating normally. We apologize for any inconvenience this may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

This incident has been resolved and all our systems are operational. The retry step, replay execution, and stop execution buttons within the debug log were non-functional from 13:39 to 15:33 GMT in all regions (US, EU, & AP). Customers may have observed pressing the retry, replay, or stop button on individual logs did not have an effect. Our engineers identified the root cause and have fixed this issue. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Workflow executions on the EU platform may have experienced some degraded performance between 14:22 GMT and 14:56 GMT. This incident has been resolved, and all our systems are operational.

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

Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

Workflows with a Gmail trigger may have experienced a deterioration of the service in both EU and AP organizations between 16:58 GMT and 18:08 GMT, with refreshing of auth failing. This incident has been resolved, and all our systems are operational. We apologize for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Between approx 23:30 UTC on 22-Feb-2025 - 19:34 UTC 24 Feb-2025, US instance users may have experienced visibility issues with the Insights component. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. This incident has been resolved and all our systems are operational. Thank you for your patience and understanding.

Between Jan 31, 2025, between 7:59 PM and 8:25 PM (GMT), EU instance users may have experienced delayed executions, API call retries and/or timeouts, or delayed initiation of executions within their workflows. This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

This incident has been resolved, and all our systems are operational. Any missing logs should now appear as expected. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue where some new executions are not appearing in the workflow logs in the US region. Execution steps are still running, but their logs may not appear. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

We are continuing to investigate this issue.

Our engineering teams are continuing to investigate this incident, in which the log search on the EU platform, has been unavailable since 13:45. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

Between 12:32 PM and 7:09 PM, users may have experienced issues with the ability to import workflows We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

Between 12:09 PM and 12:35 PM, users may have experienced the Call Connector API failing and retrying, causing slight delays in their workflow executions. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We experienced an issue with several connectors being unable to refresh their authentications. Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue that is causing unexpected behaviours within the Tray application for EU on-prem users. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

Between 11:55 AM and 12:30 PM (UTC), users may have experienced Data Storage steps failing and retrying, causing slight delays in their workflow executions. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved, and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to contact support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue that is causing an extended time between a failing step and its retry. This only affects previous failures from an earlier issue; all new failures and retries are not affected. You may experience lengthened execution times if a step in your workflow fails and attempts to retry the step. If you have any questions or concerns, please feel free to reach out to support@tray.ai

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams are continuing to monitor the results of the fix. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams are continuing to monitor the results of the fix. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams are continuing to monitor the results of the fix. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue that is causing extended time between a failing step and its retry. You will experience lengthened execution times if a step in your workflow fails and attempts to retry the step. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved and all our systems are operational. There was a 3-minute outage of Tray APIs between 15:47 and 15:50 UTC for US instances of Tray. Customers may have noticed workflow delays and delays in changes made working with the workflow builder. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

There was a 3-minute outage of Tray APIs between 15:47 and 15:50 UTC for US instances of Tray. Customers may have noticed workflow delays and delays in changes made working with the workflow builder. The issue is now resolved. We are currently investigating an issue that is caused unexpected behaviours. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue when enabling a new workflow or changing the trigger of an existing workflow for US instances. Workflows should eventually enable or reflect changes after a delay. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at support@tray.ai

This incident has been resolved and all our systems are operational. US Customers may have experienced delays when enabling a new workflow or changing the trigger of an existing workflow for US instances between 18:00 and 21:16 GMT. Workflows should eventually enable or reflect changes after the delay. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Customers may experience delays when enabling a new workflow or changing the trigger of an existing workflow for US instances starting at 18:00 GMT. Workflows should eventually enable or reflect changes after a delay. We are currently investigating an issue that is causing unexpected behaviours within the Tray application. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. During this incident, datatable connectors encountered 503 errors from 7:45 PM (BST) to 10:45 PM. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

We are currently investigating an issue affecting data tables. We apologize for any inconvenience this incident may have caused. Thank you for your understanding.

We experienced elevated latency affecting the acceptance of all triggers into Tray between 10:37 AM (BST) and 11:02 AM. The issue was swiftly identified and resolved, and normal service resumed. We apologize for any inconvenience this incident may have caused. Thank you for your understanding.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

We are currently investigating an issue causing delays in new workflow trigger executions. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at support@tray.ai

This incident has been resolved, and all our systems are operational. During this incident, short delays in workflow triggers were experienced from 6pm UTC to 6:54pm UTC in the US region. Thank you for your understanding and cooperation during this brief disruption. We appreciate your continued support as we strive to maintain the highest standards of service. If you have any questions or concerns, please feel free to reach out to support@tray.io.

We are continuing to investigate the issue which is causing delays in workflow triggers specifically.

We are currently investigating an issue causing delays in workflow executions. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at support@tray.io.

This incident has been resolved. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.ai. Thank you for your patience and understanding.

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

The issue has been identified and we are currently working on a fix to resolve this issue. We are very sorry for any inconvenience this incident may cause.

We are currently investigating an issue which is causing unexpected behaviours with CSV editor connector across all our regions. If you have any questions or concerns, please feel free to reach out to support@tray.ai.

This incident has been resolved.

A fix has been implemented for this issue, and the performance has returned to normal. We are continuing to monitor the issue to confirm.

We are currently investigating an issue that may cause degraded performance with the Embedded API. We will continue to update as the investigation continues.

A fix has been implemented for this issue, and Slack trigger performance has returned to normal.

A fix has been implemented for this issue, and Slack trigger performance has returned to normal. We are continuing to monitor the issue to confirm.

We are continuing to investigate this issue. Users will continue to see the Slack trigger fail to trigger their workflow executions. We appreciate your patience as we identify the issue, and please feel free to reach out to support@tray.io with any questions or concerns.

We are continuing to investigate this issue. Users will continue to see the Slack trigger fail to trigger their workflow executions.

We are continuing to investigate this incident. If you have any questions or concerns, please feel free to reach out to support@tray.io.

We are currently investigating an issue affecting the Slack trigger. Customers that use the Tray.io production Slack app will see issues with Slack trigger not firing. This issue does not affect customers using custom oauth apps in coordination with the Slack trigger. We will continue to update the incident as we investigate.

This incident is resolved, and workflow executions should be back to normal without delays. Please reach out to support@tray.io if you have any questions or concerns.

We are currently investigating an incident that may cause delays in workflow executions. We apologize for the inconvenience. Please reach out to support@tray.io if you have any questions or concerns on the matter, and we will continue to update here.

We have successfully rolled back a recent deployment that addressed the root cause of the issue. As a result, our Connectivity API is now fully operational and functioning as intended. The impacted period was between 10:05 and 10:24 AM (UTC). We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are currently investigating an issue that is causing unexpected behaviours when using the Tray Public API. If you have any questions or concerns, please feel free to reach out to support@tray.io.

On Jan 24 2024 between 14:55 to 15:21 UTC, we encountered a brief incident that caused timeout errors and login issues. We promptly identified the issue and released a fix. We apologize for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Our engineering teams have identified the root cause of the issue. Users may see their workflow executions to be de delayed. We apologise for the inconvenience. Please reach out to support@tray.io if you have any questions or concerns.

We are currently investigating an issue that is causing unexpected behaviours within the Tray application. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. During the incident some customers may have noticed minor delays to their executions and may have been unable to load some connectors on the canvas. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are currently investigating an issue that is causing unexpected behaviours within the Tray application. If you have any questions or concerns, please feel free to reach out to support@tray.io.

In the same time window, the application will have been unreachable. Please reach out to support@tray.io with any questions or concerns. This incident is now resolved.

Between 15:27-15:32 GMT, EU workflows may have experienced delayed workflow executions or dropped webhook triggers. The incident is now resolved, but we are continuing to monitor the situation.

This incident has been resolved. Deployment using the CDK should now be operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

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

We are currently investigating an issue regarding the use of the CDK to deploy connectors. If you have any questions or concerns, please feel free to reach out to support@tray.io.

Between 10:16 am and 11:47 am GMT, customers utilising log streaming may have experienced a disruption in receiving execution data. We have identified and rectified the issue, and normal service has been restored. To confirm, any scheduled/running executions would have proceeded as expected, however, no log streaming events would have been generated for them. We apologise for any inconvenience this incident may have caused and appreciate your patience. Please don't hesitate to reach out to support@tray.io if you encounter any further issues.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. Customers will no longer see their Gmail events to be coming through delayed. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We've identified the issue and are currently working on a fix. We will provide further updates as soon as additional information becomes available or no later than 30 minutes. Thank you for your patience.

Our teams are actively working to resolve the issue causing delays in Gmail trigger events to come through. While progress is being made, we appreciate your continued patience. We will provide further updates as soon as there is significant progress or within the next hour. Thank you for your understanding and cooperation.

Our engineering teams are actively working on resolving the issue. Customers may continue to experience delays in receiving some of their Gmail events. If you have any questions or concerns, please feel free to reach out to support@tray.io.

Our engineering teams are currently engaged in investigating this incident further. Rest assured, we are dedicated to providing you with updates as soon as they become available. Thank you for your patience.

Customers who use the Gmail Trigger may see that their events are coming through delayed. Our engineering teams are continuing to investigate this incident. We will provide further updates as soon as additional information becomes available or no later than 30 minutes.

We are currently investigating an issue that is causing a degraded behaviour for the Gmail Trigger. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Things are now back to normal. Customers will no longer see their Gmail events coming through delayed. The issue impacted our platform from 19:38 - 20:28 UTC. Our engineering team is currently monitoring the situation and continuing to investigate. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Our engineering teams are continuing to investigate this incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

We are currently investigating an issue that is causing unexpected behaviour within the Tray application. More specifically, it seems to be causing delays with the Gmail trigger. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. During the incident, some customers may have noticed minor delays to their executions and slow loading times. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are investigating an issue causing degraded performance within the Tray application. Users may experience slow loading times and delayed executions. If you have any questions or concerns, please feel free to contact support@tray.io.

This incident has been resolved.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Our engineering teams are continuing to investigate this connector incident. We will provide an update as soon as we have further information. Apologies for any inconvenience this incident may cause.

Our engineering teams are continuing to investigate this connector incident. We will provide an update as soon as we have further information. Apologies for any inconvenience this incident may cause.

Our engineering teams are continuing to investigate this connector incident. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.

We are currently investigating an issue that is causing unexpected behaviors with our Hubspot connector. You may receive 403 responses from Hubspot steps. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. The Embedded (GraphQL) API experienced a partial outage between 8:15 AM and 9:30 AM (BST). Users may have seen their GraphQL API requests receiving responses of 500s and 504s from Tray during this period. The issue occurred because of an unforeseen complication from the maintenance that we carried out earlier this morning (UK time). We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

Our engineering teams have applied a fix and are currently monitoring the results. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are currently investigating an issue that is causing unexpected behaviours with our Embedded API. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are currently investigating an issue that may cause users to be unable to configure solution instances that use the Embedded white labelled domains. If you have any questions or concerns, please feel free to reach out to support@tray.io.

We are continuing to investigate this issue. Users may have an issue loading and configuring solution instances.

We are currently investigating an issue that blocks users from logging into the Tray application. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. Users may have seen some execution slowness in the APAC region while the incident lasted. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We are currently investigating an issue that is causing workflow execution slowness within the APAC region. If you have any questions or concerns, please feel free to reach out to support@tray.io.

Our engineers have identified and resolved an issue relating to the Gmail trigger which caused degraded performance between the hours of 10:31 and 10:47 BST across all 3 regions. Please find below the exact timeframes for each region: US: 10:34 to 10:45 BST EU: 10:31 to 10:46 BST APAC: 10:32 to 10:47 BST Thank you for your understanding and cooperation during this brief disruption. We appreciate your continued support as we strive to maintain the highest standards of service.

We identified and resolved an issue relating to the Gmail trigger and Embedded API, which caused degraded performance between the hours of 14:56 to 15:02 BST in the US region. Thank you for your understanding and cooperation during this brief disruption. We appreciate your continued support as we strive to maintain the highest standards of service. If you have any questions or concerns, please feel free to reach out to support@tray.io.

Our engineers have identified and resolved an issue relating to Tray Application log in which caused degraded performance between the hours of 10:42 and 11:03 BST in the US region. Thank you for your understanding and cooperation during this brief disruption. We appreciate your continued support as we strive to maintain the highest standards of service. If you have any questions or concerns, please feel free to reach out to support@tray.io.

This incident has been resolved and all our systems are operational. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

All workflow executions are now running as expected, and customers should no longer experience throttling in their data storage steps. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please reach out to us at support@tray.io.

Our engineers have applied a fix and workflow executions are now running as expected. However, some customers may see their data storage steps to be throttled. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please reach out to us at support@tray.io.

We are currently investigating an issue causing delays in workflow executions. Additionally, users may experience retries in Data Storage steps that are configured to use the account scope. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at support@tray.io.

This incident has been resolved and all our systems are operational. Between 11:18am BST to 11:29am BST customers in the US, EU, and APAC regions experienced difficulties logging into the application. Additionally, Tray's Public API encountered errors during this period, customers may have also encountered errors with execution which would have resulted them showing as failed within the execution logs. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io.

Our engineers have identified the issue and implemented a fix for the issue. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please reach out to us at support@tray.io.

Our engineers are currently investigating an issue affecting Tray services across US, EU and APAC.

We are aware of the service degradation that occurred between 03:18 and 04:46 (UTC +1). During this period, workflow execution steps in the AP data region experienced minor delays due to repeated attempts at execution. All executions were eventually successful. Customers in this region may have noticed these delays and temporary inability to edit workflows. We have now recovered, and workflows are operating normally. We apologize for any inconvenience caused. If you have any questions or concerns, please reach out to us at support@tray.io.

We experienced a brief period of service degradation with the Trigger API between 06:01 and 06:19 AM (UTC). During this time, users may have encountered delays in processing their Trigger API events. The issue has been resolved, and the service is now operating normally. We apologize for any inconvenience this may have caused. Your satisfaction is important to us, and we appreciate your understanding and patience. If you have any questions or concerns, please contact our support team at support@tray.io.

We experienced a brief period of service degradation with the Trigger API between 15:52 and 16:08 (UTC). During this time, users may have encountered delays in processing their Trigger API events. The issue has been resolved, and the service is now operating normally. We apologize for any inconvenience this may have caused. Your satisfaction is important to us, and we appreciate your understanding and patience. If you have any questions or concerns, please contact our support team at support@tray.io.

Our engineers have identified and resolved an issue which affected Tray executions, resulting in degraded performance from 08:34 to 09:00 BST across the APAC, EU, and US regions. During this period, some workflow executions may have encountered errors. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to support@tray.io. Thank you for your patience and understanding.

We experienced a brief period of service degradation with the Tray application between 16:03 and 16:11 (BST) in all regions. During this time, users may have encountered general slowness across various features, including but not limited to running or building workflows, and calling the Connectivity, Trigger, Authentication, and Embedded APIs. The problem has been resolved, and the service is now operating normally. We apologise for any inconvenience this incident may have caused. Your satisfaction is important to us, and we appreciate your understanding and patience. If you have any questions or concerns, please contact our support team at support@tray.io.