[GH-ISSUE #574] [BUG] hanlder not found for task #276

Closed
opened 2026-03-02 05:20:07 +03:00 by kerem · 7 comments
Owner

Originally created by @mindon on GitHub (Nov 17, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/574

Originally assigned to: @hibiken on GitHub.

Describe the bug
hanlder not found for task happens sometimes

To Reproduce

  1. register 3 different patterns width HandleFunc
  2. submit 3 tasks with different patterns used above
  3. sometimes it retrying with "hanlder not found" error

Expected behavior
Not such a not-found-error

Screenshots
image

Environment (please complete the following information):

  • OS: CentOS
  • asynq v0.23.0
Originally created by @mindon on GitHub (Nov 17, 2022). Original GitHub issue: https://github.com/hibiken/asynq/issues/574 Originally assigned to: @hibiken on GitHub. **Describe the bug** hanlder not found for task happens sometimes **To Reproduce** 1. register 3 different patterns width HandleFunc 2. submit 3 tasks with different patterns used above 3. sometimes it retrying with "hanlder not found" error **Expected behavior** Not such a not-found-error **Screenshots** <img width="761" alt="image" src="https://user-images.githubusercontent.com/510257/202425965-5c6a9e36-c586-499d-be5b-1d255cf64e64.png"> **Environment (please complete the following information):** - OS: CentOS - asynq v0.23.0
kerem 2026-03-02 05:20:07 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@mindon commented on GitHub (Nov 21, 2022):

this issue comes from ErrorHandler of a worker for typename = b, telling there's no handler for typename = a

using different queue to handler different tasks

<!-- gh-comment-id:1321772722 --> @mindon commented on GitHub (Nov 21, 2022): this issue comes from ErrorHandler of a worker for typename = b, telling there's no handler for typename = a using different queue to handler different tasks
Author
Owner

@risyadaji commented on GitHub (Mar 27, 2023):

hi @mindon could you explain how you fix this issue? i have same problem

thanks before

<!-- gh-comment-id:1484406305 --> @risyadaji commented on GitHub (Mar 27, 2023): hi @mindon could you explain how you fix this issue? i have same problem thanks before
Author
Owner

@mindon commented on GitHub (Mar 29, 2023):

hi @mindon could you explain how you fix this issue? i have same problem

thanks before

@risyadaji all the queques and handlers should be matched

<!-- gh-comment-id:1487913642 --> @mindon commented on GitHub (Mar 29, 2023): > hi @mindon could you explain how you fix this issue? i have same problem > > thanks before @risyadaji all the queques and handlers should be matched
Author
Owner

@risyadaji commented on GitHub (Apr 13, 2023):

hi @mindon could you explain how you fix this issue? i have same problem
thanks before

@risyadaji all the queques and handlers should be matched

yup, i already found the solution. Thanks for the insight! @mindon

<!-- gh-comment-id:1506225367 --> @risyadaji commented on GitHub (Apr 13, 2023): > > hi @mindon could you explain how you fix this issue? i have same problem > > thanks before > > @risyadaji all the queques and handlers should be matched yup, i already found the solution. Thanks for the insight! @mindon
Author
Owner

@mohit-singh-pepper commented on GitHub (Jun 19, 2023):

@risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate.

<!-- gh-comment-id:1596765781 --> @mohit-singh-pepper commented on GitHub (Jun 19, 2023): @risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate.
Author
Owner

@mindon commented on GitHub (Jun 25, 2023):

@risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate.

it means: if there's a task request without a relative handler, you will surely get this error.

<!-- gh-comment-id:1605868690 --> @mindon commented on GitHub (Jun 25, 2023): > @risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate. it means: if there's a task request without a relative handler, you will surely get this error.
Author
Owner

@risyadaji commented on GitHub (Jul 5, 2023):

@risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate.

@mohit-singh-pepper my workaround is when enqueueing the task i put task name and also the queue name (using asynq.Queue(queueName)).

<!-- gh-comment-id:1620921343 --> @risyadaji commented on GitHub (Jul 5, 2023): > @risyadaji @mindon what do you mean by "all the queques and handlers should be matched". Can you please elaborate. @mohit-singh-pepper my workaround is when enqueueing the task i put task name and also the queue name (using `asynq.Queue(queueName)`).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#276
No description provided.