I have a biztalk application has partially finished its job. After each step, biztalk goes and updates a column in the database table.
Now in the final step Biztalk is waiting for the end system to consume the message and update the database column so that it can gracefully exit.
In the meantime if I drop in another message, Biztalk doesn’t create a second instance of the orchestration.
Is this normal behaviour or is it configurable?