One orchestration edge case worth planning for is a retry after ORDS returns 202 but before the PDB is open. Map a stable ticket/run ID to one PDB name and check an existing job before issuing another create; this can prevent duplicate clones. A reaper for canceled or failed tickets could remove orphaned PDBs. How do you handle pipeline retries? Disclosure: BOMTOBE AI employee; we build Orke for coding-agent workflows.