Jitterbit · Harmony runtime
Long running operation canceled by System
This Jitterbit message appears when an operation stuck in Submitted or Running is canceled, typically because a private agent lost contact with Harmony or the agent group had no free capacity. For private agents, confirm the agent is Running on the Agents page, review the private agent logs for connection issues, and verify a stable network connection to Harmony.
VerifiedLast verified
01Error text
Long running operation canceled by System02Likely causes
- A private agent lost its connection to Harmony and could not report operation status.
- The operation completed, but its final status was not reported back to Harmony.
- The agent group is under heavy load and is slow to pick up or update queued operations.
- No agent in the group accepted the run message because agents were offline, unhealthy or had no free capacity.
03How to fix it
- For private agents, confirm the agent is Running on the Agents page, review the private agent logs for connection issues, and verify a stable network connection to Harmony.
- Review the operation logs for errors such as 401 Unauthorized or 429 Too Many Requests.
- Keep private agents on a current version.
- Cancel the affected operations. If they cannot be canceled or the problem recurs, contact Jitterbit support.
iNotes
A 429 from the Jitterbit cloud API gateway reflects its limit of 200 requests per minute.
04Official documentation
→Related errors
- Certificate doesn't match any of the subject alternative namesThis Jitterbit error means the certificate does not include the Salesforce MyDomain or sandbox URL in its Subject Alternative Names, or the Sandbox setting on the connection is wrong. Inspect the certificate SANs with openssl x509 -in cert.crt -text -noout and confirm the MyDomain URL is listed.
- Problem with the local SSL certificate. Unable to set private key fileThis Jitterbit runtime error means the Linux private agent cannot read the private key file for an outbound mutual-TLS call. Make sure the account running the agent has read access to the key file and all parent directories.
- Maximum number of synchronous RunOperation() calls from within a While() loop has been exceededThis Jitterbit log message means a While loop made more synchronous RunOperation calls than the agent limit, which is 50 by default on agent 12.11 and later. If the loop does not check the return value, wrap the call so that reaching the limit raises an error, for example If(!RunOperation("<TAG>operation:MyOp</TAG>"), RaiseError(GetLastError()));.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries