# GetTaskQueueUserData API Always Takes 4 Minutes on Temporal v2.28.0 (PostgreSQL)

**URL:** <https://community.temporal.io/t/gettaskqueueuserdata-api-always-takes-4-minutes-on-temporal-v2-28-0-postgresql/17571>\
**Category:** Community Support\
**Tags:** java-sdk, activity, metrics\
**Created:** [May 31, 2025, 3:08pm UTC](https://community.temporal.io/t/gettaskqueueuserdata-api-always-takes-4-minutes-on-temporal-v2-28-0-postgresql/17571 "2025-05-31T15:08:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aswath\_Murugan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/aswath_murugan/32/162_2.png) [@Aswath\_Murugan](https://community.temporal.io/u/Aswath_Murugan)\
**Post date:** [May 31, 2025, 3:08pm UTC](https://community.temporal.io/t/gettaskqueueuserdata-api-always-takes-4-minutes-on-temporal-v2-28-0-postgresql/17571/1 "2025-05-31T15:08:18Z")

</div>

Hi Team,

We’re observing that the internal API call:

```auto
/temporal.server.api.matchingservice.v1.MatchingService/GetTaskQueueUserData

```

consistently takes **exactly 4 minutes (240 seconds)** in our Temporal setup:

### System Info:

- **Temporal version:** `v2.28.0`
- **Database:** PostgreSQL
- **Observability:** Prometheus + Grafana
- **Issue:** `GetTaskQueueUserData` latency is always exactly 240s, never lower, even under low load

### Questions:

1. Is it normal for `GetTaskQueueUserData` to hit a 240s response time under any condition?
2. Could a DB lock or cold cache explain this behavior?
3. Any known fixes or improvements in later versions beyond v2.28.0?

We would appreciate guidance on how to debug this and prevent the latency. Please let us know if logs, metrics, or DB schema details would help.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/a/a4b6fd328594f9f3e5114f3343a0dab59ee920e0.png)

Thanks!