Troubleshooting
Orchestrator
Unable to run job synchronously
3 min
if synchronous jobs fail, activate will fall back to asynchronous behaviour this usually appears as unexpected delays, missing feedback, or errors indicating that the web client cannot communicate with the orchestrator a common symptom is the following error unable to run job synchronously (job will continue later) one or more errors occurred no connection could be made because the target machine actively refused it (localhost 6001) what you will see the job submits instantly instead of completing synchronously no immediate results or validation feedback are returned to the user the job appears in running state in the job list with a connection refused error the job stays in the running state for up to 60 minutes , until it is detected and recovered by the orphan jobs process likely cause this issue almost always indicates that the orchestratorports configuration is incorrect or incomplete the web client cannot open a synchronous job session because the configured http/https ports are wrong the orchestrator is not listening on those ports the certificate thumbprint is invalid or out of date the port binding failed after a certificate renewal a firewall or local security tool is blocking localhost communication when the web client cannot connect, it downgrades the operation to an asynchronous submission how to resolve open activate studio navigate to resources → configuration → orchestratorports confirm that the http port is valid and listening the https port is valid and listening the certificate thumbprint matches the server’s current certificate if the certificate was recently renewed, update the thumbprint restart the orchestrator service so it can rebind the ports re run a synchronous action to confirm the behaviour is restored once the ports configuration is corrected, synchronous jobs will again complete immediately and will no longer become stranded in running state refer to docid 2ahpfceri7y6xkzpec2j1 for more detail