In the cleanup loop, each `curl -fsS -X DELETE` runs under `set -euo pipefail` with no per-id error tolerance, so a single failed DELETE (transient 5xx, rate limit, or an already-deleted deployment returning 404) aborts the step and skips every remaining id — leaving the rest of the PR's preview deployments stale, which is the leak this workflow exists to prevent. A one-line `|| echo "failed to delete $id"` per id (optionally tracking failures and exiting non-zero at the end) keeps the batch res