Vertical wrappers with cyclic dependencies

Hello @dbeltran and @bdepaula,

Summary

With cyclic dependencies (SIM depending on PP-1 and PP depending on SIM), vertical wrappers don't work, even though the workflow itself works well.

Describe your use case

I have a workflow, where the simulation jobs alternate with some intermediate processing jobs, i.e.
SIM_1 -> PP_1 -> SIM_2 -> PP_2 -> ...
Both SIM and PP are running each chunk, with dependencies: SIM depending on PP-1 and PP depending on SIM. The PP jobs do some postprocessing of the output data to then use this data as input for the next simulation. While I could include this into the simulation script, I would prefer to have it in a separate job. Further, as these jobs are all quite small jobs, I would like to pack them in a wrapper.

Describe the problem (and propose a solution if you have one)

This workflow works well without wrappers, but if you try to use a vertical wrapper, Autosubmit complains:
"Wrapper policy is set to flexible and there is a deadlock, Autosubmit will submit the jobs sequentially" Is this kind of wrappers in principle possible, or is there an intrinsic limitation?