# Handling Lack of Zone Resources in Google Batch with Seqera

**URL:** https://community.seqera.io/t/handling-lack-of-zone-resources-in-google-batch-with-seqera/1528
**Category:** Ask for help
**Tags:** google-cloud, seqera
**Created:** [December 6, 2024, 10:03pm UTC](https://community.seqera.io/t/handling-lack-of-zone-resources-in-google-batch-with-seqera/1528 "2024-12-06T22:03:24Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Abigail\_Regan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/abigail_regan/32/1172_2.png) [@Abigail\_Regan](https://community.seqera.io/u/Abigail_Regan)
#### Post date: [December 6, 2024, 10:03pm UTC](https://community.seqera.io/t/handling-lack-of-zone-resources-in-google-batch-with-seqera/1528/1 "2024-12-06T22:03:24Z")

</div>

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!