Historique des pannes de Trayio

1. 10 août 2026 à 19:26 UTCresolved

   En raison d'une dégradation du rendement de l'application, la page Facturation et utilisation était temporairement indisponible pour toutes les régions entre environ 11h00 UTC et 19h00 UTC. La facturation et l'utilisation ont été rétablies à des fonctionnalités normales. Nous nous excusons de tout inconvénient que cela pourrait avoir causé. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected]. Merci de votre patience et de votre compréhension.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 12:06 UTCinvestigating

   Nous enquêtons actuellement sur un problème affectant la connexion pour les utilisateurs se connecter par e-mail de vérification. Notre équipe d'ingénieurs s'en occupe et travaille pour rétablir le service normal le plus rapidement possible. Nous nous excusons pour tout désagrément. Si vous avez des questions entre-temps, n'hésitez pas à contacter [email protected].

2. 16 juillet 2026 à 12:28 UTCidentified

   Nous avons identifié la cause du problème. Notre équipe d'ingénieurs travaille sur un correctif et nous fournirons une nouvelle mise à jour sous peu. Nous nous excusons pour tout désagrément. Si vous avez des questions entre-temps, n'hésitez pas à contacter [email protected].

3. 16 juillet 2026 à 13:48 UTCidentified

   Notre équipe d'ingénieurs continue de travailler sur une solution. En attendant, les utilisateurs touchés peuvent se connecter via la page de connexion alternative pour leur région comme solution de rechange: États-Unis: https://app.tray.io/v2/login UE: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login Nous nous excusons pour tout désagrément. Si vous avez des questions entre-temps, n'hésitez pas à contacter [email protected].

4. 16 juillet 2026 à 14:33 UTCmonitoring

   Nous avons appliqué un correctif et la connexion devrait maintenant fonctionner comme prévu. Nous suivons la situation de près pour nous assurer que la question est entièrement résolue. Nous nous excusons pour tout désagrément. Si vous avez des questions entre-temps, n'hésitez pas à contacter [email protected].

5. 16 juillet 2026 à 14:49 UTCresolved

   Cet incident a été résolu et la connexion fonctionne maintenant comme prévu. Merci de votre patience. Si vous avez d'autres questions, n'hésitez pas à contacter [email protected].

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 13 juillet 2026 à 19:39 UTCinvestigating

   Le 13 juillet 2026, à partir de 15h20 UTC, les authentifications Gmail dans la région des États-Unis peuvent rencontrer des requêtes lorsqu'elles rafraîchissent le jeton, mais devraient finalement réussir. Nous enquêtons actuellement. Merci de votre patience et de votre compréhension. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected].

2. 13 juillet 2026 à 21:01 UTCinvestigating

   Nos équipes d'ingénieurs continuent d'enquêter sur cet incident. Nous reviendrons avec plus d'informations dès que possible. Nous sommes très désolés pour tout inconvénient que cet incident peut causer.

3. 13 juillet 2026 à 21:55 UTCidentified

   Au cours de l'enquête, nous avons isolé l'impact de deux clients et nous avons contacté ces derniers. Si vous n'avez pas reçu de message de notre part concernant cet incident, il est fort peu probable que votre organisation ait été touchée par cet incident. Nous avons identifié la cause potentielle et nous continuons d'enquêter. Nous nous excusons de tout inconvénient que cet incident pourrait avoir causé. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected]. Merci de votre patience et de votre compréhension.

4. 13 juillet 2026 à 22:32 UTCresolved

   Le 13 juillet, 2026, de 15:20 à 19:36 UTC, les authentifications Gmail dans la région des États-Unis ont peut-être rencontré des rappels de jeton qui ont finalement réussi. L'impact a été isolé à deux clients et nous avons contacté ces clients. Si vous n'avez pas reçu de message concernant cet incident, votre organisation n'aurait pas dû être touchée. Nous nous excusons de tout inconvénient que cet incident pourrait avoir causé. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected]. Merci de votre patience et de votre compréhension.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 juillet 2026 à 08:06 UTCinvestigating

   À partir de 7h00 UTC le jeudi 2 juillet 2026, certains clients de la région des États-Unis peuvent rencontrer des problèmes avec les déclencheurs programmés ne pas tirer, ce qui affecte l'exécution du workflow. Notre équipe enquête actuellement sur la cause fondamentale et travaille à une résolution. Nous fournirons d'autres mises à jour à mesure que de plus amples renseignements seront disponibles. Nous nous excusons pour tout inconvénient que cela peut causer. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected]. Merci de votre patience et de votre compréhension.

2. 2 juillet 2026 à 08:09 UTCidentified

   Nous avons identifié le problème qui cause des déclencheurs programmés de ne pas tirer, impactant l'exécution de workflow dans la région des États-Unis. Notre équipe applique actuellement un correctif et surveille de près les résultats. Nous fournirons d'autres mises à jour à mesure que de plus amples renseignements seront disponibles.

3. 2 juillet 2026 à 08:11 UTCmonitoring

   La correction pour le problème de déclenchement prévu est maintenant entrée en vigueur, et toutes les exécutions retardées de workflow ont pris du retard. Nos systèmes fonctionnent normalement depuis 7h50 UTC. Nous continuons de suivre de près la situation pour assurer la stabilité.

4. 2 juillet 2026 à 08:51 UTCresolved

   Cet incident a été résolu et tous nos systèmes sont opérationnels. Nous nous excusons de tout inconvénient que cet incident pourrait avoir causé. Si vous avez des questions ou des préoccupations, n'hésitez pas à contacter [email protected]. Merci de votre patience et de votre compréhension.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 18 juin 2026 à 16:12 UTCinvestigating

   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.

2. 18 juin 2026 à 16:13 UTCresolved

   This incident has been resolved.

1. 12 juin 2026 à 22:29 UTCresolved

   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].

1. 3 juin 2026 à 17:52 UTCresolved

   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.

1. 8 mai 2026 à 16:39 UTCinvestigating

   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].

2. 8 mai 2026 à 17:00 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 à 17:26 UTCresolved

   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.

1. 30 avril 2026 à 16:52 UTCresolved

   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]

1. 20 février 2026 à 19:30 UTCresolved

   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.

1. 15 janvier 2026 à 22:36 UTCinvestigating

   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].

2. 15 janvier 2026 à 23:14 UTCinvestigating

   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].

3. 15 janvier 2026 à 23:44 UTCinvestigating

   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].

4. 15 janvier 2026 à 23:45 UTCmonitoring

   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].

5. 15 janvier 2026 à 23:58 UTCresolved

   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.

1. 6 janvier 2026 à 11:07 UTCresolved

   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].

1. 5 janvier 2026 à 06:37 UTCinvestigating

   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.

2. 5 janvier 2026 à 06:55 UTCresolved

   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].

1. 24 décembre 2025 à 00:19 UTCinvestigating

   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].

2. 24 décembre 2025 à 01:48 UTCinvestigating

   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.

3. 24 décembre 2025 à 04:09 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 24 décembre 2025 à 06:57 UTCidentified

   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.

5. 24 décembre 2025 à 11:09 UTCidentified

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

6. 24 décembre 2025 à 11:24 UTCmonitoring

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

7. 24 décembre 2025 à 11:27 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 24 décembre 2025 à 12:04 UTCresolved

   This incident has been resolved.

1. 17 décembre 2025 à 16:35 UTCinvestigating

   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].

2. 17 décembre 2025 à 17:33 UTCmonitoring

   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].

3. 17 décembre 2025 à 18:42 UTCresolved

   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].

1. 4 décembre 2025 à 17:25 UTCinvestigating

   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].

2. 4 décembre 2025 à 18:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 décembre 2025 à 18:26 UTCresolved

   This incident has been resolved.

1. 25 novembre 2025 à 04:21 UTCinvestigating

   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.

2. 25 novembre 2025 à 05:04 UTCmonitoring

   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].

3. 25 novembre 2025 à 05:20 UTCresolved

   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].

1. 10 novembre 2025 à 16:19 UTCmonitoring

   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.

2. 10 novembre 2025 à 17:21 UTCidentified

   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.

3. 10 novembre 2025 à 18:24 UTCidentified

   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.

4. 10 novembre 2025 à 21:46 UTCidentified

   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].

5. 11 novembre 2025 à 09:57 UTCmonitoring

   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].

6. 11 novembre 2025 à 11:04 UTCresolved

   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].

1. 20 octobre 2025 à 17:58 UTCmonitoring

   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].

2. 20 octobre 2025 à 21:27 UTCresolved

   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.