A temporary order which is not a file order goes into the blacklist if it is suspended when it reach the end of the job chain

We have a job chain with one node. The node is configured to suspend the order when job has an error. When you skip the node and a temporary order is suspended then this order goes into the blacklist.

In case of a persitent order it goes to that end state which is configured in the next_state attribute of the node where the order comes from.

The temporary order should have the same behaviour then the persitent order.

In a nested job chain the order should assign to the next job chain.