Hi @tamy.santos
I’m taking advantage of this discussion thread to share that I’m experiencing a similar error in my self-hosted n8n, which I describe in the following post:
I tried to make the timeout adjustments they recommended for my Redis, but all my workflows are still queued. And before upgrading to a higher version of n8n, I would like to know if there’s something wrong with my configuration or if it’s definitely an unusual behavior of version 2.0.0.
I don’t know if maybe you’ll see some incorrect setting at first glance that could also be affecting Igor.