Automatic Batching Divergence After Failed Deployments in React 18

The application selects a publishing identity and must ensure that UI state remains consistent after a deployment failure.

React 18 automatically batches state updates originating from React's event system, but updates triggered by promises, setTimeout, or direct DOM manipulation are not batched, which can cause stale UI after a failed deployment.

Given logs that show divergent UI states, the precise impact of automatic batching on error handling and rollback strategies remains unclear, especially when third‑party libraries fire synthetic events outside React's system.

Which code paths are responsible for non‑batched updates that lead to UI divergence?

Can the batching behavior be forced or mitigated for critical state transitions during deployment?