Boomi · Boomi runtime

Process exceeded maximum execution time limit

Short answer

These log lines mean the runtime cancelled the execution because it ran longer than the Maximum Forked Execution Time in Cloud. Make the process finish sooner, for example by splitting the work, or review that property.

VerifiedLast verified

01Error text

Boomi error
Attempting to cancel execution <executionId>, started at <Start Date Time>

Aborting <Process>: Process exceeded maximum execution time limit

02Likely causes

  • The execution ran longer than Maximum Forked Execution Time in Cloud (com.boomi.container.maxExecutionTime).

03How to fix it

  1. Find the step that takes the time in the process log.
  2. Split the work into smaller executions so each finishes within the limit.
  3. If you manage the runtime cloud, review Maximum Forked Execution Time in Cloud on the Advanced properties tab.

iNotes

The docs describe the property and the message it produces. They do not give a step-by-step fix, so the steps above apply the documented property.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Boomi work:Open Boomi jobsBoomi 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.