Prefect 3.9.2 landed on November 6, 2026 as a bug fix release. The headline changes are safer lock release behavior across all three lock managers, reduced deployment write amplification from queue polling, and a long set of CLI and API output correctness fixes. Nothing here is breaking. The full release notes and downloads are on the GitHub release page.
Lock release finally behaves across managers ¶
This is the fix the release name refers to. RedisLockManager.release_lock now releases locks that were acquired asynchronously (#23654). Before this, an async acquired lock could linger in Redis after the holder thought it had released it, which blocks the next run waiting on that lock.
On top of that, MemoryLockManager and FileSystemLockManager now tolerate the release of an already expired lock (#23725). Releasing an expired lock no longer raises. If you run periodic jobs that release locks in finally blocks, this removes a class of noisy failures where the lock expired mid run.
Write volume and event pipeline ¶
One operator visible enhancement: deployment writes from queue polling are reduced (#23130). If you watch your database write metrics on a busy Prefect server, this should show up as fewer rows written per poll cycle.
On the events side, two changes worth noting. Task run events that reference a missing flow run are now dropped instead of failing the whole event batch (#23664), so one stale producer can no longer stall delivery for everyone. The event sweeper now skips locked rows (#23757), which avoids contention between the sweeper and active event processing.
Run lifecycle got cleaner too. Flow run heartbeats stop before a terminal state is proposed (#23784), and completed runs no longer crash when a lease renewal gets a 410 after reaching terminal state (#23659).
CLI and API output correctness ¶
A cluster of fixes target what your scripts actually parse:
- Literal artifact content survives in CLI JSON output (#23692), and Rich markup and emoji aliases are preserved in JSON and YAML output (#23695). If you pipe
prefectoutput into jq, the values you get back now match the values you stored. - Rich markup is disabled by default in
exit_with_error(#23763), so error text is no longer mangled for shell parsing. prefect deploymentcommands report a clear invalid name error for malformed names instead of something opaque (#23680).- The API returns 422 instead of 503 or 500 for invalid values in request bodies (#23619). Correct status codes matter if you have retry logic keyed on 5xx.
Smaller fixes that still bite in production ¶
Database and connection pool timeouts are now treated as client retryable exceptions (#23741), which changes retry behavior in your favor. GitRepository.pull_code() now honors directories changes on an existing sparse checkout (#23712). RemoteFileSystem no longer uploads every file when the ignore file excludes everything (#23786). Deployment schedule parameter overrides survive partial schedule updates (#23719). Automations keep serving triggers while the triggers service reloads them (#23778). A failed script is removed from sys.modules in load_script_as_module (#23772), so a retry after a syntax error in a flow file can pick up the corrected code.
The pydocket dependency bump and the UI dependency bumps from Dependabot are routine. Several UI only fixes, such as the timezone fallback in ui-v2, are cosmetic for data engineering purposes and are skipped here.
Where to get it ¶
- Release page: Prefect 3.9.2 on GitHub
- Repository: PrefectHQ/prefect
- Tag:
3.9.2