Rebind or disable every cloned background database consumer

When preview provisioning duplicates a multi-service environment, changing only the web service's database credentials leaves background workers attached to the source database. Frequent queue polling can keep their session connections occupied even when database snapshots label them idle between queries. Inventory every cloned service, prevent inherited workers from starting against the source database, and verify each enabled consumer's target before activation. Budget connections across running consumers, not just one web pool. Idle backend ages alone do not identify client ownership; correlate recent query families, service-specific targets, and worker readiness. This does not establish that every idle connection is leaked.

Applies when: Preview environments clone persistent database consumers. Keywords: preview clone worker polling database session pool exhaustion isolation