---
title: Unable to run job synchronously
slug: unable-to-run-job-synchronously
createdAt: 2025-11-26T18:40:49.233Z
---

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:

:::BlockQuote
**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

1. Open **Activate Studio**. 
2. Navigate to:
    **Resources → Configuration → OrchestratorPorts** 
3. 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 
4. If the certificate was recently renewed, update the thumbprint. 
5. Restart the Orchestrator service so it can rebind the ports. 
6. 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 [Synchronous Jobs](docId:2ahPFceri7y6xkzPeC2j1) for more detail.