I have a step which is marked "Always Execute", but in some cases it's just skipped/ignored completely. In this particular case I have a preceding sibling step which doesn't manage to find and allocate a particular resource, and instead of skipping it and executing the following "Always Execute" step the full execution is just aborted at that point.
Is this behavior intended? If yes, then how should I handle similar error cases?
Thanks for the info. A bug report is created as:
http://track.pmease.com/browse/QB-2995
Please watch it to get notified when it is fixed.