Trayio driftsforstyrrelser

1. 19. oktober 2026 kl. 18.49 UTCresolved

   Mellem 16: 50 og 17: 30 UTC kan nogle brugere have oplevet fejl ved implementering af Helix-projekter. Deployments mislykkedes med en "Intern server fejl" (HTTP 500), men eksisterende live-implementeringer var upåvirket. Spørgsmålet er løst, og deployeringer fungerer normalt. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. oktober 2026 kl. 16.05 UTCresolved

   Mellem 13: 15 og 13: 40 UTC, nogle brugere i den amerikanske region kan have oplevet workflow udførelse forsinkelser på op til 30 minutter. Alle henrettelser er siden blevet behandlet, og ingen data er gået tabt. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. september 2026 kl. 14.43 UTCinvestigating

   Fra 14: 08 UTC, kan brugerne have oplevet problemer med Send e-mail-stik i den amerikanske region. Vores ingeniører undersøger sagen. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai.

2. 30. september 2026 kl. 15.03 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 30. september 2026 kl. 15.14 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 30. september 2026 kl. 16.04 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. august 2026 kl. 19.26 UTCresolved

   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.

1. 16. juli 2026 kl. 12.06 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker login for brugere logge ind via e-mail verifikation. Vores ingeniørhold undersøger det og arbejder på at genoprette normal service så hurtigt som muligt. Vi undskylder for ulejligheden. Hvis du har spørgsmål i mellemtiden, er du velkommen til at række ud til support @ tray.ai.

2. 16. juli 2026 kl. 12.28 UTCidentified

   Vi har identificeret årsagen til problemet. Vores ingeniørhold arbejder på et fix og vi vil give en yderligere opdatering snart. Vi undskylder for ulejligheden. Hvis du har spørgsmål i mellemtiden, er du velkommen til at række ud til support @ tray.ai.

3. 16. juli 2026 kl. 13.48 UTCidentified

   Vores ingeniørhold arbejder videre på et fix. I mellemtiden, berørte brugere kan logge ind via den alternative login side for deres region som en workout: US: https: / / app.tray.io / v2 / login EU: https: / / app.eu1.tray.io / v2 / login AP: https: / / app.ap1.tray.io / v2 / login Vi undskylder for ulejligheden. Hvis du har spørgsmål i mellemtiden, er du velkommen til at række ud til support @ tray.ai.

4. 16. juli 2026 kl. 14.33 UTCmonitoring

   Vi har anvendt et fix og login skal nu fungere som forventet. Vi overvåger situationen nøje for at sikre, at problemet er løst. Vi undskylder for ulejligheden. Hvis du har spørgsmål i mellemtiden, er du velkommen til at række ud til support @ tray.ai.

5. 16. juli 2026 kl. 14.49 UTCresolved

   Denne hændelse er blevet løst, og login fungerer nu som forventet. Tak for din tålmodighed. Hvis du har yderligere spørgsmål, er du velkommen til at række ud til support @ tray.ai.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. juli 2026 kl. 19.39 UTCinvestigating

   Den 13. juli 2026, der starter på 15: 20 UTC, Gmail autentifications inden for den amerikanske region kan støde på genforsøg, når forfriskende token, men i sidste ende skal lykkes. Vi er ved at undersøge sagen. Tak for Deres tålmodighed og forståelse. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai.

2. 13. juli 2026 kl. 21.01 UTCinvestigating

   Vores ingeniørhold fortsætter med at undersøge denne hændelse. Vi kommer tilbage med flere oplysninger så hurtigt som muligt. Vi er meget kede af ulejligheden.

3. 13. juli 2026 kl. 21.55 UTCidentified

   I løbet af undersøgelsen isolerede vi et par kunder og kontaktede disse kunder. Hvis du ikke modtog en besked fra os relateret til denne hændelse, er det højst usandsynligt, at din organisation blev påvirket af denne hændelse. Vi har identificeret den potentielle årsag og fortsætter med at undersøge sagen. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai. Tak for Deres tålmodighed og forståelse.

4. 13. juli 2026 kl. 22.32 UTCresolved

   Den 13. juli 2026, fra 15: 20 til 19: 36 UTC, Gmail autentifikationer inden for den amerikanske region kan have mødt token genopfriskninger, der til sidst lykkedes. Virkningen var isoleret til to kunder, og vi har nået ud til disse kunder. Hvis du ikke modtog en besked relateret til denne hændelse, burde din organisation ikke have været påvirket. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai. Tak for Deres tålmodighed og forståelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 08.06 UTCinvestigating

   Startende 7: 00 UTC torsdag den 2. juli 2026, nogle kunder i den amerikanske region kan opleve problemer med skemalagte udløsere ikke fyring, hvilket er påvirker workflow udførelse. Vores team undersøger årsagen og arbejder hen imod en løsning. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai. Tak for Deres tålmodighed og forståelse.

2. 2. juli 2026 kl. 08.09 UTCidentified

   Vi har identificeret problemet, der forårsager planmæssige udløsere ikke at skyde, påvirker arbejdsgangen udførelse i den amerikanske region. Vores team anvender i øjeblikket et fix og overvåger resultaterne nøje. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

3. 2. juli 2026 kl. 08.11 UTCmonitoring

   Fixet for den planlagte udløser problem er nu trådt i kraft, og alle forsinkede arbejdsgange henrettelser er indhentet. Vores systemer har fungeret normalt siden 7: 50 UTC. Vi følger fortsat situationen nøje for at sikre stabilitet.

4. 2. juli 2026 kl. 08.51 UTCresolved

   Denne hændelse er nu løst, og alle vores systemer er operationelle. Vi undskylder for ulejligheden. Hvis du har spørgsmål eller bekymringer, er du velkommen til at række ud til support @ tray.ai. Tak for Deres tålmodighed og forståelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. juni 2026 kl. 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. juni 2026 kl. 16.13 UTCresolved

   This incident has been resolved.

1. 12. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 17.00 UTCresolved

   This incident has been resolved.

1. 7. maj 2026 kl. 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. april 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 04.09 UTCidentified

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

4. 24. december 2025 kl. 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. december 2025 kl. 11.09 UTCidentified

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

6. 24. december 2025 kl. 11.24 UTCmonitoring

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

7. 24. december 2025 kl. 11.27 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 24. december 2025 kl. 12.04 UTCresolved

   This incident has been resolved.

1. 17. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 18.24 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. december 2025 kl. 18.26 UTCresolved

   This incident has been resolved.