Hi Marco,

You may use these guides to troubleshoot:

Scheduled Execution issues - Did it not start, did it fail, or is my execution still running?

Is my scheduled execution running

Syed, I've read those articles, but not close enough it seems. Examining the Application log I find the following:
"Execution has been skipped for execution package 'A'. The project 'X' is currently executing the execution package 'B' in the process ‘timeXtender’ with process id 11500. - Scheduler, Version=20.10.19.64, Culture=neutral, PublicKeyToken=851db2ceb01ec457"

Above example relates to a situation with package B running every 5 minutes and package A being the nightly ETL process.

Package A = nightly proces, starts once a day
Package B = oparational proces, runs every 5 minutes

Wait, holdup, what does this mean? Does TX not support parallel processing of packages/executions? That would be hilarious.

I cannot imagine this being the case, can somebody point me in right direction how to properly set this up so that Package B does not prevent package A from executing?

Hi Marco,

Please study this article. 

How does the scheduler service work?

and the 2nd half of this article:

Troubleshooting concurrency issues in ODX data sources

"Even if packages from separate projects are running at the same time (or Concurrent packages set to run in one project), ensure those packages are not operating on the same tables."

You may examine the objects and settings in both packages and work with your partner to re-organize the packages for parallel processing.

Syed,

That was it, thanks!
I will have to divide these processes in separate projects, that would be more logical by default anyway. A DWH-project and some sort of ESB-project.

Thanks alot!