Automic Workload Automation

Hi Community!

Many of you have probably seen this message before but I am sure there are a large number of users who would like to know what the "interlaced" error message means:

U00007016 Task 'some_task' (RunID 'some_runid') is interlaced too much. 

You can get this error message when trying to set schedules or run forecasts among other things. The interlaced error message indicates that the system cannot determine specific upcoming events (such as when trying to run an autoforecast) because the workflows involved either contain an infinite loop (workflow calling itself) or there are specific dependencies put into place on the workflows that the system cannot determine until the actual execution of the workflow. For example, a workflow has a precondition to check the value of a specific variable created by a different task/workflow. In these cases it is simply not possible for the system to determine what is going to happen until the execution actually takes place. Actions such as autoforecasting are not possible in these situations and the workflow should be reviewed if you desire the ability to forecast.

I hope this has been helpful!

Here is another thread that also discusses about this -> https://community.automic.com/discussion/comment/26029#Comment_26029

Hi Andrew_Garland_7890

We are seeing this error message for the first time on one of our JOBS.
We recently upgraded to 12.1.1 from 12.0

Any idea if this restriction on interlacing is introduced recently or if there is some setting on the number of interlaces allowed?

Hi @John O'Mullane

Are you attempting to run an Auto Forecast or just attempting to run the job and getting this error message? If Auto Forecast is producing the error, this restriction has been in place for a significant amount of time. I believe creating a case would be warranted to review the specifics of the Job if you are receiving this error message without running the Auto Forecast.

Hope this helps!

Andrew_Garland_7890
No, it's not a forecast, it's a Job being called in a loop every 5 minutes.
We haven't seen this behavior with this Job before upgrading.

Will open a ticket, thanks anyway. 

JohnO'Mullane:
It seems, Automic introduced a restriction of rekursion in the latest versions 12.1.x and 12.0.x (in our case 12.0.4). Maximum depth seems to be 16 iterations.
We've encountered this issue right after upgrading from 12.0.3 to 12.0.4 because some scripts and jobs failed. Even some JOBFs with ACTIVATE_UC_OBJECT in PostProcess getting this error message.

Maybe you can refer to this problem:
PRB00219857                                                                                                 A Workflow activating an external Script which activates the Workflow again stops after 5 runs

rsfischer
Yes, this makes sense, thank you.
In our case it appears that it's 8 runs before it stops.