fix: Remove remaining blocking wait_for_operation calls #990
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Summary
wait_for_operationindelete_expired_instances()(VM deletion now fire-and-forget)wait_for_operationinstart_test()(VM creation now optimistic)Problem
These blocking calls were causing 504 timeouts on webhook deliveries because:
wait_for_operation(which can block for up to 30 minutes), gunicorn workers become blockedSolution
delete_expired_instances: Delete VMs without waiting for confirmation (fire-and-forget)start_test: Check for immediate errors, then record instance optimistically. If VM creation ultimately fails, the test won't report progress and will be cleaned up by the expired instances cron job.Test plan
wait_for_operationmocks)🤖 Generated with Claude Code