mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 15:35:55 +03:00
[GH-ISSUE #466] [FEATURE REQUEST] support getting state of task #2236
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#2236
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jack-evans on GitHub (May 15, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/466
Originally assigned to: @hibiken on GitHub.
Is your feature request related to a problem? Please describe.
It may be possible that on API call I enqueue a task and return a 202, but I want to provide an API that would then allow to retrieve the state of task, I.e has it been completed, is it still in progress etc
Describe the solution you'd like
The client can get a task that has been enqueued and give the state of progress.
Describe alternatives you've considered
Normally in a queuing system once something is taken off you don't then put it back on, might be a little out of scope of this project 🤔
Additional context
Add any other context or screenshots about the feature request here.
@hibiken commented on GitHub (May 15, 2022):
@jack-evans Thank you for creating an issue!
The package provide
Inspectortype which allows you to query various information from the queue, includingTaskInfo.Calling
Inspector.GetTaskInfoand inspectingTaskInfo.Stateshould give you the current state of the task in question :)LMK if you have questions!
@jack-evans commented on GitHub (May 15, 2022):
Ahh was reading the client api doc rather than the inspector 🤦 thanks!