退化应用性能-螺旋部署
Pending
受影响的组件
Helix
- resolved
在协调世界时16:50至17:30之间,一些用户在部署Helix项目时可能遭遇了失败. 部署失败时出现"内部服务器出错"(HTTP 500),但现有的活部署没有受到影响. 这个问题已经解决,部署正常进行。 我们对此事件可能造成的不便表示歉意. 如果您有任何问题或担忧, 请随意联系@tray.ai.
自动翻译自官方事件更新。
58 Trayio incidents · 2024年7月 — official updates, affected components, duration and resolution details.
在协调世界时16:50至17:30之间,一些用户在部署Helix项目时可能遭遇了失败. 部署失败时出现"内部服务器出错"(HTTP 500),但现有的活部署没有受到影响. 这个问题已经解决,部署正常进行。 我们对此事件可能造成的不便表示歉意. 如果您有任何问题或担忧, 请随意联系@tray.ai.
自动翻译自官方事件更新。
在协调世界时13:15至13:40之间,美国地区的一些用户可能经历了长达30分钟的工作流程执行延迟. 所有处决都经过处理,没有丢失任何数据。 我们对此事件可能造成的不便表示歉意. 如果您有任何问题或担忧, 请随意联系@tray.ai.
自动翻译自官方事件更新。
从协调世界时14:08起,用户可能在美国地区经历了Sende电子邮件连接器的问题. 我们的工程师正在调查这个问题。 我们为这次事件可能造成的任何不便而道歉。 如果您有任何问题或担忧, 请随意联系@tray.ai.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Due to a degradation of application performance, the Billing and Usage page was temporarily unavailable for all regions between approximately 11:00 UTC and 19:00 UTC. Billing and usage has been restored to normal functionality. 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.
我们正在调查一个影响用户通过电子邮件核查登录的问题。 我们的工程组正在调查,并努力尽快恢复正常服务. 我们为任何不便道歉。 请随意联系@tray.ai.
我们已经确定了问题的原因。 我们的工程组正在修补 我们很快会再更新 我们为任何不便道歉。 请随意联系@tray.ai.
我们的工程组正在继续修复 同时,受影响的用户可通过替代登录页面登录所在区域,作为工作轮廓: 美国:https://app.tray.io/v2/login 欧盟:https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login 页面存档备份,存于互联网档案馆. 我们为任何不便道歉。 请随意联系@tray.ai.
我们已经应用了固定,现在登录应该像预期的那样工作. 我们正在密切监测局势,以确保问题得到充分解决。 我们为任何不便道歉。 请随意联系@tray.ai.
这一事件已经解决,目前登录工作如期进行. 谢谢你的耐心 如有其他问题,请随意联系@tray.ai.
自动翻译自官方事件更新。
2026年7月13日,从协调世界时15:20起,美国区域内的Gmail认证在刷新信使时可能会遇到回覆,但最终应该成功. 我们正在调查 谢谢你的耐心和理解。 如果您有任何问题或担忧, 请随意联系@tray.ai.
我们的工程小组正在继续调查这一事件。 我们会尽快收到更多信息。 我们对这一事件可能造成的不便感到非常遗憾.
在调查期间,我们隔离了对顾客的影响,并与这些顾客联系。 如果你没有收到我们有关这起事件的讯息 你的组织很可能不会受到这一事件的影响 我们已经查明潜在原因,并正在继续调查。 我们为这次事件可能造成的任何不便而道歉。 如果您有任何问题或担忧, 请随意联系@tray.ai。 谢谢你的耐心和理解.
2026年7月13日,从协调世界时15:20到19:36,美国区域内的Gmail认证可能已经遇到最终成功的令牌刷新重试. 影响是孤立于两个客户的,我们已经联系了这些客户。 如果你没有收到与这起事件相关的信息,你的组织就不应该受到影响. 我们为这次事件可能造成的任何不便而道歉。 如果您有任何问题或担忧, 请随意联系@tray.ai。 谢谢你的耐心和理解.
自动翻译自官方事件更新。
从协调世界时2026年7月2日早上7点开始,美国地区一些客户可能会遇到预定触发器不开火的问题,这正在影响工作流程的执行. 我们的小组目前正在调查根源并努力寻求解决。 一旦获得更多信息,我们将提供进一步的最新资料。 我们对此可能造成的不便表示歉意。 如果您有任何问题或担忧, 请随意联系@tray.ai。 谢谢你的耐心和理解.
我们已查明造成预定触发点不起火的问题,影响到美国地区的工作流程执行。 我们的小组目前正在采取固定措施并密切监测结果。 一旦获得更多信息,我们将提供进一步的最新资料.
预定触发问题的解决现已生效,所有拖延执行的工作流程都已赶上。 我们的系统从协调世界时7点50分开始正常运行。 我们正在继续密切监测局势,以确保稳定.
这一事件现已得到解决,我们的所有系统都已开始运作。 我们为这次事件可能造成的任何不便而道歉。 如果您有任何问题或担忧, 请随意联系@tray.ai。 谢谢你的耐心和理解.
自动翻译自官方事件更新。
Users may be experiencing issues related to project versions across all regions. Our engineering team is currently investigating the issue and working toward a resolution. We apologise for any inconvenience this incident may have caused.
This incident has been resolved.
On 6 June 2026, some customers experienced Salesforce authentication failures, causing workflow disruptions. This was due to a 30-day refresh token TTL introduced on 7 May 2026 to meet new Salesforce security requirements. Access tokens used continuously for over 30 days had their refresh tokens expire, rendering them unusable. The issue has been resolved. Affected customers were required to re-authenticate their Salesforce connection to restore functionality. We are implementing a proactive background refresh process for Salesforce authentications to ensure tokens are refreshed before the 30-day expiry, regardless of access token usage. We apologize for any inconvenience this incident may have caused. If you have any questions or need additional details, please feel free to reach out to [email protected].
There was a span of about 10 to 15 minutes where customers may have experienced slowness or failures when creating or importing Data Tables or Vector Tables in Tray. Our engineering team has identified the root cause, resolved the incident and have restored performance of the affected services. For any users who may have experienced this degradation in performance, you may have to retry creating or importing the affected Data Table or Vector Table. If you have any questions or concerns, please reach out to to [email protected]. Thank you for your patience and understanding.
Starting at 16:15 UTC on Friday, May 8th, 2026, users may have experienced workflow failures involving Script connectors version 3.3 in the US region. 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].
This incident has been resolved.
From May 7, 2026 14:00 - 16:00 UTC, some customers may have experienced Salesforce authentication issues, including failures refreshing OAuth tokens and intermittent authentication errors when creating or re-authenticating Salesforce connections. This incident has now been resolved and all our systems are operational. A small number of customers may still need to manually re-authenticate their Salesforce connections if workflows continue experiencing authentication 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.
There was a degradation in service that caused a small number of requests to Tray webhook workflow endpoints to timeout or return a 504 status. Workflows in the Tray platform will complete successfully even though responses to the client were never sent in a minority of cases. Our engineering teams have identified the issue and resolved the root cause and 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]
From February 20, 2026 17:41 - 18:30 UTC, US Instance customers may have experienced delays and retries in executions and authentication flows. This incident has now 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.
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].
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].
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].
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].
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.
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].
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.
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].
Starting from 23:09 UTC on December 23, 2025, users with On-Prem agents in the US region may be experiencing connectivity issues. Current Impact: On-Prem agents may be unable to connect Workflows using On-Prem agents may be impacted Our engineering team is actively investigating and working to resolve this issue. We apologize for any inconvenience and will provide an update within 30 minutes. If you have any questions or concerns, please feel free to reach out to [email protected].
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.
The issue has been identified and a fix is being implemented.
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 work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Starting at 4:06 PM UTC, US Instance customers with log streaming set up may see a delay in the receipt of logs. The logs will eventually arrive; however, they are delayed. We are currently investigating 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].
A fix has been implemented and we are monitoring the result. If you have any questions or concerns, please feel free to reach out to [email protected].
Between 16:05-17:30 UTC, US Instance customers may have noticed log streaming logs were delayed and there may have been duplicate logs sent, however no logs were lost. 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].
EMEA Users leveraging the on-premise agent have been experiencing degraded performance and delayed workflow executions since 5 PM UTC. We apologize for any inconvenience this ongoing incident may be causing. If you have any questions or concerns, please feel free to contact us at [email protected].
We are continuing to investigate this issue.
This incident has been resolved.