# No Response when Requesting Regions

**URL:** https://community.coherence.io/t/no-response-when-requesting-regions/561
**Category:** Bug reports
**Created:** [August 12, 2024, 3:16pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561 "2024-08-12T15:16:53Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![michael.picerno](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@michael.picerno](https://community.coherence.io/u/michael.picerno)
#### Post date: [August 12, 2024, 3:16pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/1 "2024-08-12T15:16:54Z")

</div>

It seems from time to time my app just hangs waiting for a response when requesting regions, has there been an update or should I add some error checking here?

SDK: 1.2.3  
Unity: 6000.10f1  
OS/Platform: WebGL

---

<div class="post-metadata">

### Author: ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)
#### Post date: [August 12, 2024, 3:23pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/2 "2024-08-12T15:23:58Z")

</div>

I notice you’re using Unity 6 - is this a relatively new upgrade? Are you fetching regions asynchronously? We have experienced inconsistency with async in WebGL especially in Unity 6 in our own testing.

---

<div class="post-metadata">

### Author: ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)
#### Post date: [August 12, 2024, 3:24pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/3 "2024-08-12T15:24:55Z")

</div>

Do you experience the same issue in Unity or is this just in a WebGL build?

---

<div class="post-metadata">

### Author: ![michael.picerno](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@michael.picerno](https://community.coherence.io/u/michael.picerno)
#### Post date: [August 12, 2024, 3:48pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/4 "2024-08-12T15:48:39Z")

</div>

Unity 6 is not a new upgrade we’ve been using it for the past…month or so. It is an async call. I want to say this has become a bit more common in the past week or so? Before this Requesting regions was rather consistent.

If we already know what region we are going to use do we actually need to request the region? I wasn’t sure if there were any other initialization things going on with doing the call.

---

<div class="post-metadata">

### Author: ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)
#### Post date: [August 12, 2024, 5:30pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/5 "2024-08-12T17:30:47Z")

</div>

Nope, you do not need to request the regions. You can use the region strings as needed in other API calls.

The inconsistency you’re seeing is similar to what we’ve experienced. A build will work consistently, then a small code change will cause the webasm output to change slightly and async calls are no longer processed. We are investigating but I don’t have a timeline on it at the moment.

---

<div class="post-metadata">

### Author: ![system](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b3aa79eb9519fac7aad7eba18f15a1e8ce60f6e2.png) [@system](https://community.coherence.io/u/system)
#### Post date: [August 12, 2025, 5:31pm UTC](https://community.coherence.io/t/no-response-when-requesting-regions/561/6 "2025-08-12T17:31:28Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
