A task with name: message_when_db_updated never lands on my task server #9030
Unanswered
ultra-andy
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is weird as all get out...
I have an app service, running Django (5.0.6) on a web server and a task server. I also have a Redis server that the web and task server use for communication. The web server hands off repeating tasks to the task server, which carries out these tasks until they hit some condition and shut down. Both servers are running Docker images in Fargate instances on AWS.
I have one specific task, named message_when_db_updated which was broken, and which I've been trying to fix. The current behaviour is that when the task is triggered within my asynchronous websocket consumer:
...the task does not get run on the task server.
The following names all work, however:
mwdu_teste_aaaaaaaaa_02
massage_when_db_updated
msg_when_db_updated
I have another task named message_send which works, so it's not just an issue with message_... breaking some unspecified naming rule.
This is not sufficient information to create a bug report, but I'm not sure how best to gather relevant info - would someone please either point out some bit of documentation that I've failed to read that explains this, tell me what bits of code to look at, or how to gather meaningfully useful diagnostic information so that I can give someone more qualified than I a starting point for investigation.
Cheers.
Andrew
Beta Was this translation helpful? Give feedback.
All reactions