# Temporal-History =\> Help us understand this error! =\> Task queue range ID was 240 when it was should have been 239 **URL:** \ **Category:** Community Support\ **Tags:** history\ **Created:** [June 22, 2022, 4:44pm UTC](https://community.temporal.io/t/temporal-history-help-us-understand-this-error-task-queue-range-id-was-240-when-it-was-should-have-been-239/5036 "2022-06-22T16:44:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\ **Post date:** [June 22, 2022, 5:40pm UTC](https://community.temporal.io/t/temporal-history-help-us-understand-this-error-task-queue-range-id-was-240-when-it-was-should-have-been-239/5036/2 "2022-06-22T17:40:27Z")
> Task queue range ID was 240 when it was should have been 239\*\* This can be a transient error that can happen during restart/redeploy for example. If so you can ignore it. See similar forum post [here](https://community.temporal.io/t/error-task-queue-range-id-was-x-when-it-was-should-have-been-y/4236). > query directly though matching on non-sticky failed This error is logged [here](https://github.com/temporalio/temporal/blob/v1.13.1/service/history/historyEngine.go#L941), could you provide the entire error? Also can you assure that the task queue used by the query still has worker(s) polling it? If there is, can you see if workers are logging any errors? If there is not, that could be cause of issue (you need workers running to handle the query request). --- _[View the full topic](https://community.temporal.io/t/temporal-history-help-us-understand-this-error-task-queue-range-id-was-240-when-it-was-should-have-been-239/5036)._