Subagent disabled at Agent start cannot be enabled

Current Situation:

• When a user disables and terminates an Agent, then restarts, enables the Agent again and adds orders to a workflow then the orders enter the blocked state. After resetting the Agent, the order is no longer in the Agent's journal and becomes disrupted (failed).

Steps to reproduce:

• Create a simple Workflow.
• Disable the Agent, then terminate the Agent.
• Start the Agent and enable the Agent again.
• Add orders to a workflow; they will enter the blocked state.
• Also, by creating a new workflow and adding orders they will enter the blocked state
• Perform a reset operation on the Agent; all pending and blocked orders will move to the failed state, if we add new orders they will successfully run.

Desired Behavior:

• When we disable and terminate an Agent, then restart and enable the Agent, add orders to a workflow, the orders should not enter the blocked state.
  After resetting the Agent, the previously added orders should be executed and should finish successfully.