Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
Sonja_Bauernfeind
Digital Support
Digital Support

Update March 4th, 2026: added link to How to get Talend Management Console task schedules and pause and resume during a maintenance window using the API article
Updated April 24th, 2026: added impact on APIs (all down) and additional clarification on why tasks must be stopped and the impact on remote engines
Updated May 7th, 2026: added additional information on how to address Remote Engine impact
Updated May 12th, 2026: the anticipated impact for the remaining maintenance window has increased from 30 minutes to 90 minutes

Talend Cloud and Talend Management Console will undergo scheduled maintenance in MarchApril, and MayThis infrastructure modernization is a key step in unifying the Talend ecosystem with Qlik.

The alignment paves the way for a more seamless experience across both platforms. Over the coming months, you will gain access to integrated features that bridge data integration and analytics, enabling unified governance and a streamlined management experience across your entire data lifecycle.

The maintenance windows will occur per region, during off-peak hours, and are expected to have a maximum of 90 minutes of effective downtime. 

 

What is the expected impact?

A full outage of Talend Cloud and Talend Management Console for a duration of up to 90 minutes within a preplanned 4-hour window.

The following applications will not be accessible: 

  • Talend Management Console (TMC)
  • Talend Data Stewardship (TDS)
  • Talend Data Preparation (TDP)
  • Talend Data Inventory (TDC)
  • Talend Pipeline Designer (TPD)
  • Talend API Designer and Tester
  • Talend Studio
  • Talend Cloud Engines

All APIs for Talend Cloud will not be available during the outage. APIs impacted:

 

In detail:

  • Cloud engines will not be available, and executions running on Cloud Engines will be terminated.
  • Talend Studio users may be disconnected from their session, and it will not be possible to open a new Talend Studio session except in local mode.
  • Executions that are already in progress during the outage will terminate correctly except on cloud engines, but all tasks or plans scheduled to start during those periods will be skipped.
  • Skipped executions will not be tagged as failed, since they were never started. For this reason, check the execution status of your tasks and plans to ensure that all important ones are not skipped, or start them manually if necessary. See What do I need to do to prepare? further down in this blog post.
  • Static IP addresses for Cloud Engines corresponding to Disaster Recovery regions will change during maintenance. See What follow-up actions are required? further down in this blog post.

 

What do I need to do to prepare?

 

What follow-up actions are required?

  • After the maintenance window, check and monitor the execution status of tasks and plans, as well as the status of your Remote Engines.
    In some instances, Remote Engines might require a restart if marked as unavailable in the Talend Management Console or if tasks cannot be executed as expected.

    If restarting the Remote Engine does not resolve the complication, follow the pairing instructions in Pairing Remote Engines using a dedicated web service to reset the key and re-pair the Remote Engine.

    If your Remote Engine Gen2 is unavailable or cannot execute tasks, then:

    1. Upgrade your Remote Engine Gen2 to the latest 2026-04 release: Updating the Remote Engine Gen2 when installed using the execution script)
    2. And re-establish the pairing: Re-establish the pairing of Remote Engine Gen2

  • If you use a predefined static IP on Cloud Engine, you will need to allow the new Disaster Recovery Region's IP addresses, which will have changed at this point. While this does not immediately affect production, it will impact any potential Disaster Recovery process.

    After the maintenance window, check your static IPs (Disaster Recovery) as documented in Using predefined static IP addresses for execution containers and update your firewalls accordingly.

    No change is required for the active region's IP addresses. They will be migrated and will work as of today, ensuring no production interruption.

 

When will the maintenance take place?

Each region will undergo maintenance for 4 hours during off-peak hours, with a maximum of 90 minutes of effective downtime.

 

Region Maintenance Start Maintenance End
Talend Cloud - AWS - Asia Pacific (Sydney)

au.cloud.talend.com


Wednesday 25 March 2026
 
22:00 AEDT (Sydney)

UTC: 25/03/26 - 11:00


Thursday 26 March 2026
 
02:00 AEDT (Sydney)

UTC: 25/03/26 - 15:00

Talend Cloud - AWS - Asia Pacific (Tokyo)

ap.cloud.talend.com


Monday 20 April
2026 
22:00 JST (Tokyo)

UTC: 20/04/26 - 13:00


Tuesday 21 April
2026 
02:00 JST (Tokyo)

UTC: 20/04/26 - 17:00

Talend Cloud - AWS - US East (N. Virginia)

us.cloud.talend.com


Monday 27 April 2026
 
02:00 EDT

UTC: 27/04/26 - 6:00


Monday 27 April
2026 
06:00 EDT

UTC: 27/04/26 - 10:00

Talend Cloud - AWS - Europe (Frankfurt)

eu.cloud.talend.com


Tuesday 26 May
2026 
21:00 CEST

UTC: 26/05/26 - 19:00


Wednesday 27 May
2026 
01:00 CEST

UTC: 26/05/26 - 23:00

To identify which region your tenant is affected by, cross-reference Accessing Talend Cloud applications.

To track further updates during the scheduled Qlik Cloud Maintenance, please visit our Qlik Cloud Status page. This blog post will be updated with additional information where necessary. 

 

Thank you for choosing Qlik,
Qlik Support

26 Comments
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Ed6 

Thank you for reaching out. Once again, the concern is fully understood and the feedback appreciated. I'm taking it to the relevant groups.

All the best,
Sonja

0 Likes
278 Views
ext_kalb
Contributor
Contributor

Hello,

We have hundreds of Talend jobs and Talend plans running across multiple remote engine clusters. Several jobs run every minute.
If I understand correctly, we need to pause everything before the maintenance work and restart everything afterward. We’ll then have to manually start some of them afterward. This means there will be more than 4 hours during which these many processes are not running. When the processes restart after maintenance, they will have a huge amount of data to process. That will take time as well. The target systems will then receive the data up to 5 hours late in some cases.
That is extremely bad and hardly acceptable.

Why does it say “maximum 30 minutes” in one place and “4 hours” in another?
Will we be notified promptly when we can restart the Talend jobs?

Best regards
Mathias

222 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @ext_kalb 

I fully understand your feedback and have forwarded it to the relevant teams. We do appreciate the input.

Now, as to the two different times: While the maintenance will take 4 hours (the time window to take into account), the impact on services is 90* minutes. Keeping subscribed to the status page will help with staying informed about when the maintenance progresses.

And lastly: Do you want me to get you in touch with someone to discuss the maintenance and preparation with you? 

 

All the best,
Sonja 

 

*The time window was updated last week - if you still see 30 minutes somewhere, let me know so I can have it reviewed. 

0 Likes
180 Views
ext_kalb
Contributor
Contributor

Hello Sonja,
Thank you for letting us know that the time has been increased from 30 to 90 minutes.

We have now written a Java program that pauses and starts our job tasks and plans.

However, we have to run this at least 15 minutes before the maintenance window so that the jobs are finished by the time the window starts. But if Qlik’s approval for use doesn’t come until the end of the four-hour window, it will still take time for us to check and start everything. In that case, many critical and important processes might not have run for 5 hours. That would be very bad.

What are the chances that we'll be able to start it up again in two hours?

Best regards
Mathias

0 Likes
117 Views
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @ext_kalb 

I've reached out to my subject matter experts internally, and we'd like to encourage you to log a support ticket. This'll allow one of our experts to speak to your specific concerns directly.

Let me know if you need any help with a case.

All the best,
Sonja

 

0 Likes
86 Views
cocop10
Contributor
Contributor

Bonjour,

Que devons-nous faire lors de cette maintenance, couper les flux en amont ?
L'ensemble de nos flux ne seront exécutables ?

0 Likes
67 Views