55 Trayio incidents · luglio 2024 — official updates, affected components, duration and resolution details.
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.
Stiamo attualmente indagando su un problema che riguarda il login per gli utenti che effettuano l'accesso via e-mail di verifica. Il nostro team di ingegneria sta cercando in esso e lavorando per ripristinare il servizio normale il più rapidamente possibile. Ci scusiamo per qualsiasi inconveniente. Se avete domande nel frattempo, non esitate a contattare [email protected].
Abbiamo identificato la causa del problema. Il nostro team di ingegneri sta lavorando a una soluzione e forniremo un ulteriore aggiornamento a breve. Ci scusiamo per qualsiasi inconveniente. Se avete domande nel frattempo, non esitate a contattare [email protected].
Il nostro team di ingegneri continua a lavorare su una soluzione. Nel frattempo, gli utenti interessati possono accedere tramite la pagina di login alternativa per la loro regione come soluzione di lavoro: USA: https://app.tray.io/v2/login UE: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login Ci scusiamo per qualsiasi inconveniente. Se avete domande nel frattempo, non esitate a contattare [email protected].
Abbiamo applicato una correzione e il login dovrebbe funzionare come previsto. Stiamo monitorando la situazione da vicino per garantire che il problema sia completamente risolto. Ci scusiamo per qualsiasi inconveniente. Se avete domande nel frattempo, non esitate a contattare [email protected].
Questo incidente è stato risolto e il login sta ora funzionando come previsto. Grazie per la pazienza. Se avete ulteriori domande, non esitate a contattare [email protected].
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Il 13 luglio 2026, a partire dalle 15:20 UTC, le autenticazione Gmail all'interno della regione degli Stati Uniti possono incontrare ripetizioni quando si aggiorna il token, ma alla fine dovrebbe avere successo. Stiamo indagando. Grazie per la vostra pazienza e comprensione. Se avete domande o dubbi, non esitate a contattare [email protected].
I nostri team di ingegneri continuano a indagare su questo incidente. Torneremo con ulteriori informazioni il prima possibile. Siamo molto dispiaciuti per qualsiasi inconveniente che questo incidente possa causare.
Durante l'indagine, abbiamo isolato la coppia di impatto dei clienti e raggiunto verso quei clienti. Se non avete ricevuto un messaggio da noi relativo a questo incidente, è altamente improbabile che la vostra organizzazione è stata influenzata da questo incidente. Abbiamo identificato la causa potenziale e stiamo continuando a indagare. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Se avete domande o dubbi, non esitate a contattare [email protected]. Grazie per la vostra pazienza e comprensione.
Il 13 luglio 2026, dalle 15:20 alle 19:36 UTC, le autenticazione Gmail all'interno della regione degli Stati Uniti possono aver incontrato token rinfreschi che alla fine sono riusciti. L'impatto è stato isolato a due clienti e abbiamo raggiunto quei clienti. Se non hai ricevuto un messaggio relativo a questo incidente, la tua organizzazione non avrebbe dovuto essere influenzata. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Se avete domande o dubbi, non esitate a contattare [email protected]. Grazie per la vostra pazienza e comprensione.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
A partire dalle 7:00 UTC di giovedì 2 luglio 2026, alcuni clienti della regione degli Stati Uniti possono avere problemi con i trigger programmati che non sparano, che sta influenzando l'esecuzione del flusso di lavoro. Il nostro team sta attualmente indagando sulla causa principale e lavorando verso una risoluzione. Forniremo ulteriori aggiornamenti in quanto ulteriori informazioni diventano disponibili. Ci scusiamo per qualsiasi inconveniente che possa causare. Se avete domande o dubbi, non esitate a contattare [email protected]. Grazie per la vostra pazienza e comprensione.
Abbiamo identificato il problema causando trigger programmati di non sparare, impatto esecuzione del flusso di lavoro nella regione degli Stati Uniti. Il nostro team sta attualmente applicando una correzione e il monitoraggio dei risultati da vicino. Forniremo ulteriori aggiornamenti in quanto ulteriori informazioni diventano disponibili.
La correzione per il problema di attivazione programmata ha ora preso effetto, e tutte le esecuzioni del flusso di lavoro ritardato sono state recuperate. I nostri sistemi sono operativi normalmente dalle 7:50 AM UTC. Stiamo continuando a monitorare attentamente la situazione per garantire la stabilità.
Questo incidente è stato risolto e tutti i nostri sistemi sono operativi. Ci scusiamo per qualsiasi inconveniente che questo incidente possa aver causato. Se avete domande o dubbi, non esitate a contattare [email protected]. Grazie per la vostra pazienza e comprensione.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
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.
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].
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].
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.
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.
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.
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].
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].
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].
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].
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.