Hey there Joshua,
Apologies - I must have missed that constraint where you’re not wanting to have serial execution; my mistake, however I’d suggest a following possible change to make this work, but if you have a lot of combinations you’re trying to manage, then this idea would fail:
- Model A & B within the same job template
- Make sure they’re in separate <agent> tags - parallelism will be obtained via Horde as a result.
- Have job C be chained with the first
Now, should this still not be feasible, yes the manual invocation via rest API is an option. To your point, the node will “fire and forget”. You could write your task such that you query the resulting job to see for completion, but you’d effectively be holding that agent until a result is arrived at (and pending the duration of that job, it may not be advisable to do so!).
Let me know what you’re thinking on this - happy to keep brain storming.
Kind regards,
Julian