unity-batch

Batch processing in Unity lets you query, preview, and apply changes to many GameObjects at once. It uses a preview-confirm-execute workflow with a confirmToken, so you can review property or material impacts before applying mutations, preventing costly errors across large scenes.

The best way to replace materials across multiple Unity GameObjects is to use a batch query to select targets, generate a preview to confirm the material replacement impact, and then execute the approved changes asynchronously with progress tracking and retry-on-failure support.

You monitor progress for large async Unity scene cleanup jobs by requesting a jobId during execution. You can then query job status, fetch logs, wait for completion, or cancel the operation, while receiving progress events as the batch processes chunks of changes.

Yes, this batch processing approach works with Unity assets and components. You can use unified filters to retrieve and target GameObjects, components, and assets for operations like fixing missing scripts, standardizing naming, setting render layers, and cleaning up temp helpers.

If an async Unity batch operation fails partway through, the system generates a batch report. You can retrieve this report to identify failed items and use the built-in retry-on-failure mechanism to reapply the confirmed changes selectively.

Yes, you can cancel a Unity batch job after it has started executing. When you run your preview-confirmed mutations asynchronously with a jobId, the system exposes a cancel function that stops the ongoing operation safely.