Jitterbit · Scripts

Maximum number of synchronous RunOperation() calls from within a While() loop has been exceeded

Short answer

This 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()));.

VerifiedLast verified

01Error text

Jitterbit error
Maximum number of synchronous RunOperation() calls from within a While() loop has been exceeded.

02Likely causes

  • An agent-level limit, MaxSynchronousRunOperationCallsInLoop in the [OperationEngine] section of jitterbit.conf (default 50), caps synchronous calls per While loop.
  • Past the limit, each further call returns false without raising an error.

03How to fix it

  1. 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()));.

iNotes

RunOperation, RunOperationFromProject and ReRunOperation share one cumulative count per loop.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.