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
Attempting to cancel execution <executionId>, started at <Start Date Time>
Aborting <Process>: Process exceeded maximum execution time limit02Likely causes
- The execution ran longer than Maximum Forked Execution Time in Cloud (
com.boomi.container.maxExecutionTime).
03How to fix it
- Find the step that takes the time in the process log.
- Split the work into smaller executions so each finishes within the limit.
- 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
→Related errors
- Process discarded due to system load: execution queue maximum size reachedThis message means the node's execution queue was full, so the runtime discarded the submitted process instead of queuing it. Reduce how many executions arrive at once, or review the Maximum Queued Executions per Node and Maximum Simultaneous Executions per Node properties.
- SecurityException: Exceeded thread limitThis exception means a forked execution or an execution worker tried to use more threads than the runtime allows. Lower the parallelism in the process, or review the Maximum Execution Threads property.
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