Handling Lack of Zone Resources in Google Batch with Seqera

Hello, I’m trying to trigger a pipeline in Seqera using tower webhooks, but I’m running into issues with zone availability in google cloud. In order to resolve these errors, I have had to manually change the action itself since I noticed that Seqera would hang in a “submitted” state if the zone didn’t have enough compute resources. I also tried to pass google zones as a part of http requests for the tower webhook, but I didn’t have success with this.

With this in mind, I was wondering if there was any precedent for how I should be managing Seqera to allow it auto-rotate through zones to choose one that has availability? Is their any functionality that would perform this that I may not have run in to? If not, what is the best practice for rotating through zones or waiting for zone availability?
Thanks!