What causes the flushing-queries physics error in Godot?

Physics state was mutated during a physics callback — freeing bodies, toggling collision shapes, changing monitoring, or moving static bodies inside body_entered / area_entered while the physics server is locked.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “Can't change this state while flushing queries. Use call_deferred()” in Godot

Q: How do you fix the flushing-queries physics error in Godot?

Defer every physics mutation made from physics callbacks: call_deferred() for property changes and queue_free()-style deferral for removals, or use set_deferred() for flags like monitoring and disabled.

Quick answer: Defer every physics mutation made from physics callbacks: call_deferred() for property changes and queue_free()-style deferral for removals, or use set_deferred() for flags like monitoring and disabled.

The physics server locks its state while delivering collision callbacks; touching it during the lock raises this. The rule is one word — defer — applied everywhere it fires. Here is the map.

How to fix it

1. Defer shape and monitoring flips

Inside callbacks write collision_shape.set_deferred("disabled", true) and area.set_deferred("monitoring", false) — direct assignment is the error.

2. Defer frees and reparents

Use queue_free() (already deferred) for bodies, and call_deferred("add_child", node)/call_deferred("reparent", ...) for structure changes triggered by collisions.

3. Batch pickup logic

For pickups: mark collected, hide visuals, defer the physical removal — the player perceives instant pickup while physics stays consistent.

4. Search callbacks for direct mutations

Grep your _on_body_entered-style handlers for physics property writes; any direct one is a latent version of this error under load.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.