- Detected by Pingoru
- May 08, 2026, 03:15 PM UTC
- Resolved
- May 08, 2026, 05:00 PM UTC
- Duration
- 1h 45m
Affected: Workflow ExecutionOtherWorkflow Triggers
Timeline · 2 updates
-
investigating May 08, 2026, 04:39 PM UTC
Starting at 4:15 UTC on Friday, May 8th, 2026, users may have experienced workflow failures involving Script connectors across all regions. Our engineering team is actively investigating the 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 [email protected].
-
resolved May 08, 2026, 05:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 09:30 AM UTC
- Resolved
- Apr 28, 2026, 09:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 30, 2026, 04:52 PM UTC
On April 28th at approximately 09:30 AM UTC, there was a degradation in service that caused requests to Tray webhook workflow endpoints to timeout or return a 504 status. Workflows in the Tray platform will appear to have completed successfully even though responses to the client were never sent. Our engineering teams have identified the issue and resolved the root cause as of April 30th at 02:43 AM UTC. We will continue to monitor performance of the webhook workflows and ensure their reliability. If you have any questions, feel free to reach out to [email protected]
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 10:36 PM UTC
- Resolved
- Jan 15, 2026, 11:58 PM UTC
- Duration
- 1h 21m
Affected: Other
Timeline · 5 updates
-
investigating Jan 15, 2026, 10:36 PM UTC
Starting from January 14, 2026, users who have Office 365 authentications created using the Tray Production OAuth app may have seen authentications fail and are unable to re-authenticate. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
investigating Jan 15, 2026, 11:14 PM UTC
We have identified the issue and our engineering teams are investigating a potential resolution. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to [email protected].
-
investigating Jan 15, 2026, 11:44 PM UTC
Our engineers have deployed a potential fix. We are currently monitoring to see if the issue resolves. Thank you for your patience and understanding. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
monitoring Jan 15, 2026, 11:45 PM UTC
On January 14, 2026 at 2:42:50 PM to January 15, 2026 at 11:31:03 PM UTC, users who have Office 365 authentications created using the Tray Production OAuth app may have seen authentications fail and are unable to re-authenticate. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
resolved Jan 15, 2026, 11:58 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jan 06, 2026, 11:07 AM UTC
- Resolved
- Jan 06, 2026, 11:07 AM UTC
- Duration
- —
Affected: Merlin Agent Builder
Timeline · 1 update
-
resolved Jan 06, 2026, 11:07 AM UTC
Between 10:08 AM UTC and 10:49 AM UTC, some users may have encountered errors when using the Tray Native AI model within Merlin Agent Builder workflows. Other models were unaffected. The issue has been resolved, and services are now operating normally. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- Jan 05, 2026, 06:37 AM UTC
- Resolved
- Jan 05, 2026, 06:55 AM UTC
- Duration
- 18m
Affected: Merlin Agent Builder
Timeline · 2 updates
-
investigating Jan 05, 2026, 06:37 AM UTC
We are currently investigating an issue affecting Merlin Agent workflows from around 5:00 AM UTC. AP instance users may notice 500 errors in Merlin Agent workflows. We apologise for any inconvenience this incident may cause. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.
-
resolved Jan 05, 2026, 06:55 AM UTC
Between 05:00 - 05:55 UTC, AP Instance customers may have noticed errors in Merlin Agent 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 [email protected].
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 04:21 AM UTC
- Resolved
- Nov 25, 2025, 05:20 AM UTC
- Duration
- 59m
Affected: Workflow ExecutionConnectors API
Timeline · 3 updates
-
investigating Nov 25, 2025, 04:21 AM UTC
We are currently investigating an issue affecting workflow step execution and CAPI that started at around 3:50 AM UTC. US instance users may notice poor performance, including slow connector executions and sporadic connector failures. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.
-
monitoring Nov 25, 2025, 05:04 AM UTC
We are actively monitoring the fix implemented for this issue. Users may still experience degraded performance resulting in slow connector executions. We thank you for your patience and apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
resolved Nov 25, 2025, 05:20 AM UTC
The incident is resolved and executions should be returned to normal. We thank you for your patience and apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 04:19 PM UTC
- Resolved
- Nov 11, 2025, 11:04 AM UTC
- Duration
- 18h 45m
Affected: Other
Timeline · 6 updates
-
monitoring Nov 10, 2025, 04:19 PM UTC
An issue is ongoing since November, 8 2025, 12:04PM BST. US instance users may have noticed the Send Email connector versions 3.0 and below may have appeared to execute successfully, however emails may have not actually been sent. A workaround for this issue is to upgrade to version 4.1 of this connector. We have identified the issue with connector version 3.0 and below and are currently investigating a potential resolution. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.
-
identified Nov 10, 2025, 05:21 PM UTC
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.
-
identified Nov 10, 2025, 06:24 PM UTC
Our engineering teams have also identified the services involving reset password emails, adding new users emails and notification emails are also affected. We will be back with more information as soon as possible. We are very sorry for any inconvenience this incident may cause.
-
identified Nov 10, 2025, 09:46 PM UTC
We are currently awaiting a response from a third-party service to implement a potential solution. We thank you for your patience and apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
monitoring Nov 11, 2025, 09:57 AM UTC
We are actively monitoring the fix implemented for this issue. We thank you for your patience and apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
resolved Nov 11, 2025, 11:04 AM UTC
This incident is resolved, users are now able to receive password reset, new user invites and notification emails. We also recommend any users still using the older version of Send Email connector to upgrade to the latest version (4.1) as soon as possible. We thank you for your patience and apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 05:58 PM UTC
- Resolved
- Oct 20, 2025, 09:27 PM UTC
- Duration
- 3h 29m
Affected: Insights, Usage and Logs
Timeline · 2 updates
-
monitoring Oct 20, 2025, 05:58 PM UTC
Starting on October 17, 2025 at 2:00 pm EST, US Instances users may have experienced delays in receiving log streaming logs. Our engineering team has implemented a fix and are currently monitoring the progress. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
resolved Oct 20, 2025, 09:27 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:36 AM UTC
- Resolved
- Oct 20, 2025, 10:36 AM UTC
- Duration
- 59m
Affected: Workflow ExecutionWorkflow Triggers
Timeline · 2 updates
-
identified Oct 20, 2025, 09:36 AM UTC
There are ongoing issues with the Slack application and platform. Due to this issue, users may also experience delays with the Slack Trigger within Tray.ai. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected]. Thank you for your patience and understanding.
-
resolved Oct 20, 2025, 10:36 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 01:41 PM UTC
- Resolved
- Aug 01, 2025, 02:36 PM UTC
- Duration
- 55m
Affected: Workflow Execution
Timeline · 4 updates
-
investigating Aug 01, 2025, 01:41 PM UTC
At 14:22 PM BST, users may have experienced issues with the workflow executions in the APAC region. We apologise for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
-
monitoring Aug 01, 2025, 02:22 PM UTC
Our engineering teams have applied a fix at 15:05 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 [email protected]. Thank you for your patience and understanding.
-
monitoring Aug 01, 2025, 02:23 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 01, 2025, 02:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2025, 11:31 AM UTC
- Resolved
- Jun 25, 2025, 10:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 25, 2025, 11:31 AM UTC
Between 11:10 AM BST and 11:28 AM BST, users in the US region may have experienced delays of up to approximately 10 minutes when processing trigger updates to workflows, initializing new workflows, or processing changes to existing triggers. We apologize for any inconvenience this incident may have caused. If you have any questions or concerns, please feel free to reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 02:55 PM UTC
- Resolved
- Jun 18, 2025, 03:04 PM UTC
- Duration
- 8m
Affected: Workflow Execution
Timeline · 2 updates
-
investigating Jun 18, 2025, 02:55 PM UTC
Beginning at 14:40 GMT, EU customers may have begun experiencing issues with executions of their on-prem connectors. We are investigating at this time and will continue to update the status here. Please reach out to [email protected] if you have any questions or concerns at this time.
-
resolved Jun 18, 2025, 03:04 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:27 PM UTC
- Resolved
- Jun 12, 2025, 07:22 PM UTC
- Duration
- 54m
Affected: Workflow ExecutionWorkflow Triggers
Timeline · 2 updates
-
investigating Jun 12, 2025, 06:27 PM UTC
Beginning at 18:11 GMT, users may have begun experiencing issues with the Gmail trigger. Customers on the EU server may have had difficulties logging in to the Tray application as well. 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 [email protected].
-
resolved Jun 12, 2025, 07:22 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 03:20 PM UTC
- Resolved
- Jun 10, 2025, 03:46 PM UTC
- Duration
- 25m
Affected: Workflow ExecutionOther
Timeline · 2 updates
-
identified Jun 10, 2025, 03:20 PM UTC
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.
-
resolved Jun 10, 2025, 03:46 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2025, 02:56 PM UTC
- Resolved
- Jun 10, 2025, 03:07 PM UTC
- Duration
- 11m
Affected: Other
Timeline · 2 updates
-
monitoring Jun 10, 2025, 02:56 PM UTC
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 [email protected]. Thank you for your patience and understanding.
-
resolved Jun 10, 2025, 03:07 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2025, 10:35 PM UTC
- Resolved
- Mar 27, 2025, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 27, 2025, 10:35 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2025, 04:21 PM UTC
- Resolved
- Mar 11, 2025, 04:21 PM UTC
- Duration
- —
Affected: Workflow Builder Logs
Timeline · 1 update
-
resolved Mar 11, 2025, 04:21 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2025, 02:22 PM UTC
- Resolved
- Mar 11, 2025, 02:55 PM UTC
- Duration
- 32m
Affected: Workflow Execution
Timeline · 3 updates
-
investigating Mar 11, 2025, 02:39 PM UTC
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.
-
monitoring Mar 11, 2025, 02:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 11, 2025, 02:55 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 31, 2025, 12:54 AM UTC
- Resolved
- Jan 31, 2025, 01:48 AM UTC
- Duration
- 54m
Affected: Workflow Execution
Timeline · 2 updates
-
investigating Jan 31, 2025, 12:54 AM UTC
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 [email protected].
-
resolved Jan 31, 2025, 01:48 AM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2025, 10:13 PM UTC
- Resolved
- Jan 21, 2025, 10:13 PM UTC
- Duration
- —
Affected: Workflow Execution
Timeline · 1 update
-
resolved Jan 21, 2025, 10:13 PM UTC
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 [email protected].
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2025, 02:10 PM UTC
- Resolved
- Jan 13, 2025, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 14, 2025, 02:10 PM UTC
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 [email protected].
Read the full incident report →
- Detected by Pingoru
- Dec 06, 2024, 06:04 PM UTC
- Resolved
- Dec 06, 2024, 06:20 PM UTC
- Duration
- 16m
Affected: Other
Timeline · 2 updates
-
monitoring Dec 06, 2024, 06:04 PM UTC
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 [email protected]. Thank you for your patience and understanding.
-
resolved Dec 06, 2024, 06:20 PM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2024, 01:15 PM UTC
- Resolved
- Nov 27, 2024, 01:15 PM UTC
- Duration
- —
Affected: Workflow ExecutionOther
Timeline · 1 update
-
resolved Nov 27, 2024, 01:15 PM UTC
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 [email protected].
Read the full incident report →
- Detected by Pingoru
- Nov 22, 2024, 04:12 PM UTC
- Resolved
- Nov 22, 2024, 04:15 PM UTC
- Duration
- 3m
Affected: Workflow ExecutionWorkflow Builder APIEmbedded APIConnectors APITriggers API
Timeline · 2 updates
-
investigating Nov 22, 2024, 04:12 PM UTC
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 [email protected].
-
resolved Nov 22, 2024, 04:15 PM UTC
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 [email protected].
Read the full incident report →
- Detected by Pingoru
- Oct 11, 2024, 09:18 PM UTC
- Resolved
- Oct 14, 2024, 11:53 AM UTC
- Duration
- 2d 14h
Timeline · 3 updates
-
investigating Oct 11, 2024, 09:18 PM UTC
We are currently investigating an issue affecting data tables. We apologize for any inconvenience this incident may have caused. Thank you for your understanding.
-
monitoring Oct 11, 2024, 10:15 PM UTC
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 [email protected]. Thank you for your patience and understanding.
-
resolved Oct 14, 2024, 11:53 AM UTC
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 [email protected]. Thank you for your patience and understanding.
Read the full incident report →
