Orchestration executions failing for Prepare Instance

Full error message from Orchestration portal:

 

TimeXtender failed to run task

Logfile output: 

2:35:54 PM UTC now: 4/14/2025 2:35:54 PM
2:35:54 PM TimeXtender Version 25.1.0.29 built 3/21/2025 1:48:12 PM. Running on 
2:35:54 PM PID: 3561  - Started with arguments: --startpkg 76 --email user@company.com --error_email user@company.com --uat PROD --token  --customerkey company --user 13 --use-saas-queue true --is-saas-local true 
2:35:54 PM Connected at 4/14/2025 2:35:54 PM
2:35:54 PM Flushing jobs in job queue that are not running on system
2:35:54 PM 
2:35:54 PM ** Executing package TestOrchOrchestrationPackage
2:35:54 PM 
2:35:54 PM Package finished in under a minute on last successful run
2:35:54 PM 
2:35:55 PM Adding task to job queue with PID 35612, UAT PROD, TaskId 76 and TaskType EBI_PACKAGE
2:35:55 PM Starting to execute the prepare package 'TestOrch'
2:36:55 PM TimeXtender Data Integration task has not started executing yet. If you are having issues with your tasks please look at our troubleshooting guide at https://support.timextender.com/timextender-orchestration-139/troubleshooting-timextender-data-integration-in-orchestration-3218
2:45:56 PM ### TimeXtender error message ####################
TimeXtender Data Integration task did not start within the expected time, please make sure the service running your instance is working correctly by looking at our troubleshooting guide at https://support.timextender.com/timextender-orchestration-139/troubleshooting-timextender-data-integration-in-orchestration-3218
2:45:56 PM ##################################################
2:45:56 PM ### TimeXtender execution log ####################
TimeXtender failed to run task
2:45:56 PM ##################################################
2:45:56 PM Execution failed: TimeXtender failed to run task
2:45:56 PM Sending error e-mail.
2:45:56 PM  Sending mail to user@company.com
2:45:56 PM Update audit execution information

Hi ​@oscarcleve 

I have created a support ticket for this

This issue appears to have been resolved by restarting the execution service

​@Christian Hauggaard , restarting the service only solved the problem temporarily. Today the problem is back. Services have been restarted and are running.