Skip to main content
SUBMITTED

Multiple running Prepare jobs in one execution service

  • September 25, 2024
  • 4 replies
  • 61 views

Roy V
Problem Solver
Forum|alt.badge.img+3

Hello

I see two tickets for it not being possible to have multiple jobs running at the same time. The answer was that it is not posibble within one execution service (only for ssl now).
With more and more organisations moving to more real time analysis, timextender is the ideal tool to have multiple job schedules during the day (even with extract data on demand to have it combined with data ingestion). But then you are limited, that for one instance, it can only have one job running and other jobs have to wait. I just don’t understand how that matches with the filosofy of the tool?
I hope that based on the related tickets a solution to this issue is one of high priority.

The wo tickets:

 

If not high on the priority list can you please let me know how we can solve this in the meantime (of course without using the development or acceptance execution service for production jobs).
For example : one job runs each hour and one each two hours. When the 2-hour job is running the job which needs to run each hour will not run while the two hour job is busy (and runs for an hour and a half). I don’t want a technical limit on these times, it needs to be based on the business needs.

4 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • TimeXtender Xpert
  • September 25, 2024

Hi @Roy V ,

 

there is a fix for running multiple SSL at once in one Job in the same ExecutionEngine in the latest release, see here: 

 


Roy V
Problem Solver
Forum|alt.badge.img+3
  • Author
  • Problem Solver
  • September 25, 2024

Thanks for the update Rory. I saw that already but in our case the jobs are datawarehouse jobs, not ssl.


rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • TimeXtender Xpert
  • September 25, 2024

Hi @Roy V ,

 yes that is not possible right now - should improve in future. 


Roy V
Problem Solver
Forum|alt.badge.img+3
  • Author
  • Problem Solver
  • September 25, 2024

Indeed, but for us this is not an improvement, it’s a bug as we had this implemented in the legacy  version but can not use it now when you are migrated to the saas version. So hopefully the future comes soon :-)