Issue: Remote Engine does not receive artifact from TMC
Some customers of our company are experiencing issues with scheduling via TMC.
Basically, when it is time to run a task, TMC fetches the job artifact from an S3 bucket that Qlik Talend internally uses and sends the .zip file to the remote engine selected for execution.
This happens if it is the first time the artifact has been published (either a new artifact or an updated version of an existing one), or if some time has passed since the last time TMC sent the artifact to the remote engine (basically refreshing the cache on the remote engine).
In the last few days we have been encountering the following error:
Warning: Error resolving artifact actions.demo_doc_extract.work:DocExtractDispatch:zip:0.1.1.20260503043119: [Could not transfer artifact actions.demo_doc_extract.work:DocExtractDispatch:zip:0.1.1.20260503043119 from/to 6820ceee-ae27-4afd-b652-cd8d557ca6b3.release (s3://eu-production-minio-artifacts/repositories/6820ceee-ae27-4afd-b652-cd8d557ca6b3/): Could not download resource repositories/6820ceee-ae27-4afd-b652-cd8d557ca6b3/actions/demo_doc_extract/work/DocExtractDispatch/0.1.1.20260503043119/DocExtractDispatch-0.1.1.20260503043119.zip]
Error: Could not transfer file
TMC tries a few times to send the artifact. Sometimes it resolves itself, other times the execution fails because it cannot transfer the artifact. this uncertainty is making process unreliable.
Based on the error and behavior you described, the failure is occurring during the artifact retrieval phase, before the job is executed on the Remote Engine.
When a task runs in Talend Management Console, the platform retrieves the job artifact from Talend-managed object storage and transfers it to the Remote Engine. In your case, the error indicates that this download step is intermittently failing:
“Could not transfer artifact”
“Could not download resource from s3://eu-production-minio-artifacts”
Since the same artifact sometimes succeeds and sometimes fails, this points to a transient issue in the artifact delivery path, rather than a problem with the job itself or its configuration.
The most common causes for this pattern are:
Temporary instability or latency in the underlying artifact storage service
Network or proxy-related interruptions between the Remote Engine and the artifact endpoint
Timing-related issues when the Remote Engine needs to refresh its local cache
Because the behavior is intermittent and impacts reliability, the next steps are:
Review Remote Engine logs during a failure to identify any network timeouts or connection issues
Use a Remote Engine specific script, talend-re-helper.sh or talend-re-helper.bat, to collect context information about the issues you encountered. You can then use this information yourself or send it to the Qlik Support team for engine troubleshooting. Only the information stored under the <RemoteEngineInstallation> folder and its sub-folders is collected. If you have configured your Remote Engine to place some working files outside the <RemoteEngineInstallation> folder, these files cannot be collected. Note: Only a Remote Engine from v2.10.7 and onwards supports this script.
Confirm whether this affects multiple artifacts or engines
Optionally configure retries on task execution to mitigate transient failures
