Istoricul incidentelor Trayio

1. 10 august 2026 la 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.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 12:06 UTCinvestigating

   Investigăm o problemă care afectează logarea utilizatorilor prin verificarea e-mail. Echipa noastră de inginerie este în căutarea în ea și de lucru pentru a restabili serviciul normal cât mai repede posibil. Ne cerem scuze pentru neplăceri. Dacă aveți întrebări între timp, vă rugăm să nu ezitați să ajungeți la [email protected].

2. 16 iulie 2026 la 12:28 UTCidentified

   Am identificat cauza problemei. Echipa noastră de inginerie lucrează la un fix și vom oferi o actualizare în curând. Ne cerem scuze pentru neplăceri. Dacă aveți întrebări între timp, vă rugăm să nu ezitați să ajungeți la [email protected].

3. 16 iulie 2026 la 13:48 UTCidentified

   Echipa noastră de inginerie continuă să lucreze la un fix. Între timp, utilizatorii afectați se pot conecta prin intermediul paginii alternative de conectare pentru regiunea lor ca o soluție: US: https://app.tray.io/v2/login UE: https://app.eu1.tray.io/v2/login AP: https://app.ap1.tray.io/v2/login Ne cerem scuze pentru neplăceri. Dacă aveți întrebări între timp, vă rugăm să nu ezitați să ajungeți la [email protected].

4. 16 iulie 2026 la 14:33 UTCmonitoring

   Am aplicat un fix și login ar trebui să fie acum de lucru așa cum era de așteptat. Monitorizăm îndeaproape situaţia pentru a ne asigura că problema este pe deplin rezolvată. Ne cerem scuze pentru neplăceri. Dacă aveți întrebări între timp, vă rugăm să nu ezitați să ajungeți la [email protected].

5. 16 iulie 2026 la 14:49 UTCresolved

   Acest incident a fost rezolvat și login este acum de lucru așa cum era de așteptat. Mulţumesc pentru răbdare. Dacă aveți întrebări suplimentare, vă rugăm să nu ezitați să ajungeți la [email protected].

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 19:39 UTCinvestigating

   La 13 iulie 2026, începând cu ora 15:20 UTC, autentificarea Gmail în regiunea SUA poate avea loc atunci când se reîmprospătează jetonul, dar în cele din urmă va avea succes. În prezent investigăm. Vă mulţumesc pentru răbdare şi înţelegere. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la [email protected].

2. 13 iulie 2026 la 21:01 UTCinvestigating

   Echipele noastre de ingineri continuă să investigheze acest incident. Vom reveni cu mai multe informații cât mai curând posibil. Ne pare foarte rău pentru orice inconveniente pe care acest incident le poate cauza.

3. 13 iulie 2026 la 21:55 UTCidentified

   În timpul anchetei, am izolat câţiva clienţi şi am ajuns la acei clienţi. Dacă nu ați primit un mesaj de la noi legat de acest incident, este foarte puțin probabil ca organizația dumneavoastră să fi fost afectată de acest incident. Avem o cauză potenţială identificată şi continuăm să investigăm. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la [email protected]. Vă mulţumesc pentru răbdare şi înţelegere.

4. 13 iulie 2026 la 22:32 UTCresolved

   La 13 iulie 2026, de la 15:20 la 19:36 UTC, autentificările Gmail în regiunea SUA s-ar putea să fi întâlnit retiri de reîmprospătare care în cele din urmă au reușit. Impactul a fost izolat la doi clienți și am ajuns la acești clienți. Dacă nu aţi primit un mesaj legat de acest incident, organizaţia dumneavoastră nu ar fi trebuit să fie afectată. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la [email protected]. Vă mulţumesc pentru răbdare şi înţelegere.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 08:06 UTCinvestigating

   Începând de joi, 2 iulie 2026, la ora 7:00 AM UTC, unii clienţi din regiunea SUA s-ar putea confrunta cu probleme cu declanşatori programaţi care nu trag, ceea ce afectează execuţia fluxului de lucru. Echipa noastră investighează în prezent cauza principală și lucrează la o rezoluție. Vom furniza actualizări suplimentare pe măsură ce vor fi disponibile mai multe informații. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la [email protected]. Vă mulţumesc pentru răbdare şi înţelegere.

2. 2 iulie 2026 la 08:09 UTCidentified

   Am identificat problema care a determinat declanşatorii programaţi să nu tragă, influenţând execuţia fluxului de lucru în regiunea SUA. Echipa noastră aplică în prezent un fix și monitorizarea îndeaproape a rezultatelor. Vom furniza actualizări suplimentare pe măsură ce vor fi disponibile mai multe informații.

3. 2 iulie 2026 la 08:11 UTCmonitoring

   Fixarea pentru problema de declanșare programată a intrat în vigoare acum, și toate execuția întârziată a fluxului de lucru au prins. Sistemele noastre funcţionează normal de la ora 7:50 AM UTC. Continuăm să monitorizăm îndeaproape situaţia pentru a asigura stabilitatea.

4. 2 iulie 2026 la 08:51 UTCresolved

   Acest incident a fost rezolvat şi toate sistemele noastre sunt operaţionale. Ne cerem scuze pentru orice neplăceri pe care acest incident le-a cauzat. Dacă aveți întrebări sau preocupări, vă rugăm să nu ezitați să ajungeți la [email protected]. Vă mulţumesc pentru răbdare şi înţelegere.

Traducere automată din actualizarea oficială a incidentului.

1. 18 iunie 2026 la 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 iunie 2026 la 16:13 UTCresolved

   This incident has been resolved.

1. 12 iunie 2026 la 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 iunie 2026 la 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 la 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 la 17:00 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 la 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 aprilie 2026 la 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 februarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 04:09 UTCidentified

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

4. 24 decembrie 2025 la 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 decembrie 2025 la 11:09 UTCidentified

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

6. 24 decembrie 2025 la 11:24 UTCmonitoring

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

7. 24 decembrie 2025 la 11:27 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 24 decembrie 2025 la 12:04 UTCresolved

   This incident has been resolved.

1. 17 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 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 decembrie 2025 la 18:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 decembrie 2025 la 18:26 UTCresolved

   This incident has been resolved.

1. 25 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 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.