When multiple sessions are opened to a REST host, only the latest session can be used successfully.
API calls using the older sessions then fail with the below error:
"error_code": 403
"error_message": "The credentials were incorrect or the account specified has been locked."
Orchestrator 8.x
The REST host may not be configured in Orchestrator with setting "Support for parallel request executions" (enableParallelRequests).
If that setting is not enabled, then Orchestrator will cache details of one session and try to use that for any further calls to the same REST host.
Re-add the REST host in Orchestrator ensuring that checkbox "Support for parallel request executions" is selected.
This should allow multiple simultaneous sessions to the same REST host from an Orchestrator workflow.