58 Trayio incidents · 2024年7月 — official updates, affected components, duration and resolution details.
16:50 と 17:30 UTC の間、Helix プロジェクトをデプロイする際に、一部のユーザーは、問題が発生する可能性があります。 「内部サーバエラー」(HTTP 500)で展開が失敗しましたが、既存のライブ展開は影響を受けません。 問題は解決され、展開は正常に機能しています。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい.
公式のインシデント更新を自動翻訳しています。
13:15〜13:40 UTCの間、米国地域での一部のユーザーは、最大30分でワークフローの実行遅延が発生することがあります。 処理が進んでおり、データが失われることはありません。 ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい.
公式のインシデント更新を自動翻訳しています。
14:08 UTC から始まると、米国地域での送信メールコネクターに問題が発生します。 エンジニアは課題を調査しています。 万が一、この事故に遭ったお詫び申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
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.
現在、メール検証でログインしているユーザーのログインに影響を及ぼす問題について調査しています。 当社のエンジニアリングチームは、可能な限り迅速に正常なサービスを回復するために探しています。 不便をおかけいたしますが、 ご質問は、[email protected]までお気軽にお問い合わせください.
問題の原因を特定しました。 当社のエンジニアリングチームは、修正に取り組んでおり、さらにアップデートを短時間で提供します。 不便をおかけいたしますが、 ご質問は、[email protected]までお気軽にお問い合わせください.
当社のエンジニアリングチームは、修正作業を継続しています。 その間、影響を受けたユーザーは、その地域の代替ログインページを介して、回避策としてログインすることができます。 米国: https://app.tray.io/v2/login EU: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login 不便をおかけいたしますが、 ご質問は、[email protected]までお気軽にお問い合わせください.
修正とログインが期待通りに機能するようになりました。 問題が完全に解決されるように、状況を密接に監視しています。 不便をおかけいたしますが、 ご質問は、[email protected]までお気軽にお問い合わせください.
このインシデントは解決され、ログインが期待どおりに機能しています。 ありがとうございます。 ご不明な点がございましたら、[email protected]までお気軽にお問い合わせください.
公式のインシデント更新を自動翻訳しています。
2026年7月13日、15:20 UTC で始まる Gmail 認証は、トークンを爽やかにすると、アメリカ地域内の Gmail 認証は、レトリーに遭遇する可能性がありますが、最終的には成功する必要があります。 現在調査中です。 誠に有難うございます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい.
当社のエンジニアリングチームは、この事件を調査し続けています。 弊社では、可能な限り迅速に対応いたします。 大変ご迷惑をおかけいたしますが、何卒ご了承くださいますようお願い申し上げます.
調査中は、お客様のインパクトカップルを隔離し、そのお客様にお越しいただきました。 この事件に関連した当社からのメッセージが届かない場合は、この事件に影響を及ぼしたと思われがちです。 潜在的な原因を特定し、調査を継続しています。 万が一、この事故に遭ったお詫び申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい。 誠に有難うございます.
2026年7月13日、15:20から19:36 UTC、米国地域におけるGmail認証は、最終的に成功したトークンリフレッシュレトリーに遭遇する可能性があります。 お客様には、その影響が2社に隔離され、お客さまにその影響を受けました。 このインシデントに関連したメッセージを受信しなかった場合、組織は影響を受けるべきではありません。 万が一、この事故に遭ったお詫び申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい。 誠に有難うございます.
公式のインシデント更新を自動翻訳しています。
2026年7月2日(木)に7:00 UTCを始動し、米国地域での一部の顧客は、ワークフローの実行に影響を及ぼすスケジュールされたトリガーの問題が発生することがあります。 当社のチームは、現在、根本的な原因を調べ、解決に向けて取り組んでいます。 情報が増えるにつれて、さらなるアップデートが提供されます。 不便をおかけしますが、お詫び申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい。 誠に有難うございます.
米国の地域でのワークフローの実行に影響を与え、火にならないスケジュールされたトリガーを引き起こした問題を特定しました。 当社のチームは、現在、結果の修正と監視を密接に適用しています。 情報が増えるにつれて、さらなるアップデートが提供されます.
スケジュールされたトリガーの問題の修正が有効になり、すべての遅延したワークフローの実行が巻き込まれました。 当社のシステムは、通常、7:50 AM UTC 以降で動作しています。 今後も状況を監視し、安定性を確保し続けます.
このインシデントは解決され、すべてのシステムが運用されています。 万が一、この事故に遭ったお詫び申し上げます。 ご不明な点がございましたら、お気軽に[email protected]までお問い合わせ下さい。 誠に有難うございます.
公式のインシデント更新を自動翻訳しています。
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.
