Hi!
I am guessing this logic in every job is why it is taking a while to generate the full master workflow.
=> possibly yes but without knowning the whole monster-structure its hard to tell :-)
Usually a couple of get_vars do not produce that heavy system workload...
If I changed every job to generate at execution would I just be moving this time taken further down the chain? I am thinking this code needs to execute at some point so whether that is at activation or execution that time taken will be the same?
=> Yes exactly, the generation time will not be reduced but shifted. Thats a common step to "reduce" the actvation time at the start of bigger workflows. Activation of the single tasks is not perceived that long.
Also, sorry ..... normally the workflow takes about 5 mins from activation to start ... on the odd occasion it takes over 10 minutes ... any idea where a good place to start would be in terms of finding any potential bottle necks?
=> You could put a JOBI in your generic JOBI containing a put_var &LOGVARA# with Object name, timestamp parent etc.
then you can check where is the longest activation time of your subtasks
cheers, Wolfgang