Data service and Route deployment and execution when communication with Talend Remote Engine is lost
Last updated: 10/16/2026The log and metric collection will continue as well, but as the Talend Remote Engine uses a fixed buffer size for log collection, depending on the amount of log data send from the microservices or Talend Runtime, it may not be able to buffer all log data for the transfer to Talend Cloud. Therefore, the log and metric data records may not be transferred to Talend Cloud when the Talend Remote Engine buffer is fully used. However, as soon as the network connection is established again, the buffered log data will be resent automatically, as well as the new log and metric data.
Any new deployment or undeployment request for Routes and data services to Talend Remote Engine will fail if network communication is not possible.
Status of tasks after a prolonged engine outage
The status of a running Routes and Data Services in the Talend Management Console can become inaccurate if the Talend Remote Engine stays unavailable for a long time.
A periodic check runs every 8 hours. If the check finds a Route or Data Service task running on an unavailable engine for at least 6 hours, it marks this task as Failed in the Talend Management Console. When the engine is available again, the task runs normally, but its status remains Failed until the next check, which can be up to 8 hours later. To correct the status immediately, undeploy and redeploy the task.
The table shows how the duration of an engine outage affects the status of Route or Data Service tasks in the Talend Management Console.
| Engine unavailable for | Result |
|---|---|
| Less than 6 hours | The Talend Management Console never marks running Route or Data Service tasks as Failed. |
| At least 6 hours but less than 14 hours | The Talend Management Console marks running Route or Data Service tasks as Failed only if a periodic check runs while the engine has been unavailable for at least 6 hours. The result depends on when the outage starts relative to the checks. |
| At least 14 hours | The Talend Management Console always marks running Route and Data Service tasks as Failed. |
The examples assume that periodic checks run every 8 hours, at 00:00, 08:00, and 16:00.
| Engine unavailable | Result | Explanation |
|---|---|---|
| Connectivity lost at 07:59 for a few minutes | Not marked | At the 08:00 check, the engine has been unavailable for only a few minutes. |
| Maintenance from 08:01 to 15:01 (7 hours) | Not marked | The engine is available again before the 16:00 check, even though the
outage lasts at least 6 hours. This outage is not detected because of the specific check timing in this example. |
| Maintenance from 08:01 to 16:30 (8.5 hours) |
Running Route or Data Service tasks are marked Failed at 16:00. After the engine is available again at 16:30, the tasks run normally, but their status remains Failed until the 00:00 check. |
The engine has been unavailable for almost 8 hours at the 16:00 check. |
| Unplanned power outage from 12:00 to 01:00 the next day (13 hours) | Running Route or Data Service tasks are marked Failed at the 00:00 check. After the engine is available again at 01:00, the tasks run normally, but their status remains Failed until the 08:00 check. | The engine has been unavailable for 12 hours at the 00:00 check. |
-
For planned maintenance in which the engine will be unavailable for at least 6 hours, consider undeploying Route or Data Service tasks before maintenance and redeploying them afterward. Do not rely on timing because you do not control when a check runs.
-
After an unplanned outage, such as a power outage, check the status of your Route or Data Service tasks in the Talend Management Console once the engine is available again. If a running task has the status Failed with the message Execution marked as failed due to missing execution status info from engine, wait for the next check, or consider undeploying and redeploying the task to correct the status immediately.