You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the samples that use redis where workers are separate generates non-stop errors
like the following:
2025/09/15 23:01:02 ERROR error polling task error="dequeueing task: NOGROUP No such key 'task-stream:system:activities' or consumer group 'task-workers' in XREADGROUP with GROUP option"
The original error occurred because:
* The worker tries to recover abandoned tasks during startup using XAUTOCLAIM
* This requires existing consumer groups for the Redis streams
* Previously, consumer groups were only created when PrepareWorkflowQueues/PrepareActivityQueues were explicitly called
* The recovery operations happened before queue preparation, causing NOGROUP errors
The fix ensures that consumer groups for the essential queues (default and _system_) are created automatically during Redis backend initialization, eliminating the race condition.
0 commit comments