Most Boomi incidents are not caused by exotic bugs. They come from ordinary design decisions: a process that keeps running with zero documents, a map that silently loses logic after a profile change, or a deployment that fails at the worst moment because the account ran out of connection licenses. This guide collects the platform changes that address those situations and the design habits that prevent them, so processes behave predictably in production.

1. Stop processing when there is nothing to process

A classic failure mode: a connector query returns no records, but the process continues. Downstream shapes run without data, maps produce empty output, a target connector is called with nothing, and the result is a confusing exception or a flood of log lines.

Since the January 2026 release, Boomi has a process option called Stop If No Documents, on the Process Options tab:

• When enabled, execution halts at any step that produces zero documents, so subsequent shapes do not run.
• The execution log shows a clear message – “No documents found. Skipping execution for the step.” – so operations understands why a path stopped.
• The option is enabled by default for processes created after the January 2026 release; existing processes keep their behaviour until you change it, and the Start shape panel recommends enabling it when it is off.

How I apply it:

1. Enable it on scheduled and polling processes – “nothing new since the last run” is a normal outcome there, not an error.
2. Think twice on processes where an empty result is a signal. If a daily file is expected and missing, you want an alert, not a silent stop. Handle that explicitly with a decision step and a notification before the point where the process would stop.
3. Retest existing processes before switching the option on. Branches that relied on running with zero documents, for example to write a “no data” status record, will stop doing so.

2. Protect map logic when profiles change

For years, changing the source or destination profile of a Map component cleared all mappings, including function logic. Teams learned to avoid profile changes or to rebuild maps by hand. Since November 2025 the map is smarter: when a profile changes, only the directly affected mappings are removed, and function logic and unrelated connections are preserved.

That makes profile evolution practical, but it does not make it risk-free. A review routine for every profile change:

1. Compare the old and new profile and list removed or renamed elements.
2. Open every map that uses the profile and check that the mappings to those elements were rebuilt.
3. Check functions whose inputs were affected – a function that kept its output mapping but lost an input still produces wrong data.
4. Run a regression test with representative documents, including optional and repeating elements.
5. Use the component diff during merge review to confirm exactly what changed in the map.

3. Treat connection licensing as a deployment risk

Connection licensing has gone through several changes, and the current behaviour can block a deployment if nobody watches it:

• 2023 – Boomi added a licensing report showing which connectors are used across the account, where they are used, and whether they are inherited.
• September 2024 – the license audit logic was disabled by default, with an account preference to enable warnings and deployment restrictions when the account is in overage.
• September 2025 – the License Enforcement feature was retired. Since the platform release of September 13, 2025, when an account has used all available connection licenses, new connections cannot be deployed until licenses are purchased or freed. Processes that are already deployed keep running, and over-deployed accounts see a warning under Settings > Account > Licensing.

The design consequence: every new connection component that is deployed can consume a license. Practical habits:

• Reuse connections per system and environment instead of creating a new connection component per process; combined with Global Variables this is easier than ever.
• Include license headroom in release planning. A go-live that adds three new systems needs three free licenses in production.
• Review the licensing page monthly and free connections from retired integrations.

4. Make dynamic connections explicit

Dynamic process connection properties let a single process set connection values at runtime – useful for multi-tenant scenarios. Since September 2025 they also support OAuth 2.0 authorization parameters and access token parameters defined in the connection component. Use the feature, but keep the logic that decides the values in one place, log which target was selected (never the secret), and validate the inputs before they reach the connection.

5. Start new processes from a template, not a blank canvas

Boomi’s integration quick start wizard, introduced in 2023, creates a starting process from a few questions. It is a good way to begin, but production processes need more than a working path. A team template should contain:

• A standard error-handling sub-process with try/catch and a notification or exception queue.
• Correlation ID creation or propagation at the start of the process.
• Tracked fields that support searching in Process Reporting.
• Process options set deliberately, including Stop If No Documents.
• Step notes that explain non-obvious design choices.

6. Plan retention for audit questions

Standard process reporting retention is limited. For regulated environments, Boomi introduced Local Execution History Archiving in March 2026 for customers with the Extended Process Reporting add-on, to retain execution summaries and artifacts beyond the standard 18-month policy. Decide early which integrations fall under audit requirements and configure retention for them, instead of discovering the gap when the auditor asks.

Production review checklist

• Stop If No Documents set deliberately; expected-but-missing data raises an alert.
• Profile changes reviewed map by map, including function inputs.
• Connections reused per system; license headroom checked before go-live.
• Dynamic connection logic centralized and logged without secrets.
• Error handling, correlation ID and tracked fields from the team template.
• Retention requirements documented per integration.

For operational monitoring of listener-based processes, see Boomi listener workers: reliability and operations.

Sources

• Boomi Integration Release Notes, January 2026
• Boomi Integration Release Notes, November 2025
• Boomi Integration Release Notes, September 2025
• Boomi Platform Release – September 2024
• Boomi Platform Release – March 2026