Historial de interrupciones de Trayio

1. 10 de agosto de 2026 a las 19:26 UTCresolved

   Debido a la degradación del rendimiento de las aplicaciones, la página Facturación y Uso no estaba disponible temporalmente para todas las regiones entre aproximadamente 11:00 UTC y 19:00 UTC. La facturación y el uso se han restaurado a la funcionalidad normal. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected]. Gracias por su paciencia y comprensión.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de julio de 2026 a las 12:06 UTCinvestigating

   Actualmente estamos investigando un problema que afecta el inicio de sesión de usuarios a través de la verificación de correo electrónico. Nuestro equipo de ingeniería está investigando y trabajando para restaurar el servicio normal lo antes posible. Nos disculpamos por cualquier inconveniente. Si tienes alguna pregunta mientras tanto, por favor no dudes en contactar a [email protected].

2. 16 de julio de 2026 a las 12:28 UTCidentified

   Hemos identificado la causa del problema. Nuestro equipo de ingeniería está trabajando en una solución y proporcionaremos una actualización más en breve. Nos disculpamos por cualquier inconveniente. Si tienes alguna pregunta mientras tanto, por favor no dudes en contactar a [email protected].

3. 16 de julio de 2026 a las 13:48 UTCidentified

   Nuestro equipo de ingeniería continúa trabajando en una solución. Mientras tanto, los usuarios afectados pueden iniciar sesión a través de la página de inicio de sesión alternativa para su región como solución de trabajo: US: https://app.tray.io/v2/login EU: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login Nos disculpamos por cualquier inconveniente. Si tienes alguna pregunta mientras tanto, por favor no dudes en contactar a [email protected].

4. 16 de julio de 2026 a las 14:33 UTCmonitoring

   Hemos aplicado una solución y el login debe estar trabajando como se espera. Estamos monitoreando la situación de cerca para asegurar que el problema se resuelva completamente. Nos disculpamos por cualquier inconveniente. Si tienes alguna pregunta mientras tanto, por favor no dudes en contactar a [email protected].

5. 16 de julio de 2026 a las 14:49 UTCresolved

   Este incidente se ha resuelto y ahora la conexión está funcionando como se espera. Gracias por su paciencia. Si tiene alguna otra pregunta, no dude en contactar a [email protected].

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de julio de 2026 a las 19:39 UTCinvestigating

   El 13 de julio de 2026, a partir de las 15:20 UTC, las autenticaciones de Gmail dentro de la región de EE.UU. pueden encontrar retries cuando refrescan la señal, pero eventualmente deben tener éxito. Actualmente estamos investigando. Gracias por su paciencia y comprensión. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected].

2. 13 de julio de 2026 a las 21:01 UTCinvestigating

   Nuestros equipos de ingeniería continúan investigando este incidente. Volveremos con más información lo antes posible. Lo sentimos mucho por cualquier inconveniente que pueda causar este incidente.

3. 13 de julio de 2026 a las 21:55 UTCidentified

   Durante la investigación, aislamos el impacto de los clientes y llegamos a esos clientes. Si usted no recibió un mensaje de nosotros relacionado con este incidente, es muy poco probable que su organización fue impactada por este incidente. Hemos identificado la causa potencial y seguimos investigando. Nos disculpamos por cualquier inconveniente que este incidente pueda haber causado. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected]. Gracias por su paciencia y comprensión.

4. 13 de julio de 2026 a las 22:32 UTCresolved

   El 13 de julio de 2026, de 15:20 a 19:36 UTC, las autenticaciones de Gmail dentro de la región de EE.UU. pueden haber encontrado retretes de refresco que eventualmente tuvieron éxito. El impacto fue aislado a dos clientes y hemos llegado a esos clientes. Si no recibió un mensaje relacionado con este incidente, su organización no debería haber sido afectada. Nos disculpamos por cualquier inconveniente que este incidente pueda haber causado. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected]. Gracias por su paciencia y comprensión.

Traducido automáticamente desde la actualización oficial del incidente.

1. 2 de julio de 2026 a las 8:06 UTCinvestigating

   A partir de las 7:00 AM UTC el jueves, 2 de julio de 2026, algunos clientes de la región de Estados Unidos pueden estar experimentando problemas con los disparadores programados que no disparan, lo que está impactando la ejecución del flujo de trabajo. Nuestro equipo está investigando la causa raíz y trabajando para una resolución. Proporcionaremos más actualizaciones a medida que se disponga de más información. Nos disculpamos por cualquier inconveniente que esto pueda causar. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected]. Gracias por su paciencia y comprensión.

2. 2 de julio de 2026 a las 8:09 UTCidentified

   Hemos identificado el problema causando desencadenantes programados para no disparar, impactando la ejecución del flujo de trabajo en la región de Estados Unidos. Nuestro equipo está aplicando actualmente una solución y monitoreo de los resultados de cerca. Proporcionaremos más actualizaciones a medida que se disponga de más información.

3. 2 de julio de 2026 a las 8:11 UTCmonitoring

   La solución para la cuestión de los desencadenantes programados ha entrado en vigor, y todas las ejecuciones de los flujos de trabajo retrasados han alcanzado el límite. Nuestros sistemas han estado operando normalmente desde las 7:50 AM UTC. Seguimos vigilando de cerca la situación para garantizar la estabilidad.

4. 2 de julio de 2026 a las 8:51 UTCresolved

   Este incidente ha sido resuelto y todos nuestros sistemas están operativos. Nos disculpamos por cualquier inconveniente que este incidente pueda haber causado. Si tiene alguna pregunta o preocupación, por favor no dude en contactar a [email protected]. Gracias por su paciencia y comprensión.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de junio de 2026 a las 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 de junio de 2026 a las 16:13 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 17:00 UTCresolved

   This incident has been resolved.

1. 7 de mayo de 2026 a las 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 de abril de 2026 a las 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 de febrero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 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 de enero de 2026 a las 6: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 de enero de 2026 a las 6: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 de diciembre de 2025 a las 0: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 de diciembre de 2025 a las 1: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 de diciembre de 2025 a las 4:09 UTCidentified

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

4. 24 de diciembre de 2025 a las 6: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 de diciembre de 2025 a las 11:09 UTCidentified

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

6. 24 de diciembre de 2025 a las 11:24 UTCmonitoring

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

7. 24 de diciembre de 2025 a las 11:27 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 24 de diciembre de 2025 a las 12:04 UTCresolved

   This incident has been resolved.

1. 17 de diciembre de 2025 a las 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 de diciembre de 2025 a las 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 de diciembre de 2025 a las 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 de diciembre de 2025 a las 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 de diciembre de 2025 a las 18:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 de diciembre de 2025 a las 18:26 UTCresolved

   This incident has been resolved.

1. 25 de noviembre de 2025 a las 4: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 de noviembre de 2025 a las 5: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 de noviembre de 2025 a las 5: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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 9: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 de noviembre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 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.