Hello!
I’m facing a big problem with queues in some scenarios.
I’ve already opened several tickets for make automation, I even recorded 3 videos. Their feedback is always that the DEV team is working to adjust and thanking me for reporting, but it’s been 3 months and no change and almost every month at least 3 or 5 times I need to run scenarios by hand, pressing the play 1 for 1.
Are you in the community also facing the same problem? There is a queue, but the scenario does not process the queue even if you turn it off and on, remove it from the sequential process, nothing works.
On the 3rd and 24th of December there were problems that even caused them to take action, in make.status it talks more about it, but here the problem still persists.
Hello @Joao_Cruz, welcome to the community and thanks for raising this here.
We experienced an issue yesterday with records being stuck in the queue. However, the issue has now been resolved. All the queued records should now be processed and everything should function as expected.
Feel free to test on your end to see if everything is working for you.
Thank you very much for your patience and understanding and we apologize for any inconvenience this may have caused. 
Hello @Michaela , thanks for the answer!
The problem still persists, I emailed the support ticket again today. Yesterday night it actually started running again here, but this afternoon I experienced the same problem again.
Ticket: #1324564
One way I found to get around this is to program the scenario to run every 1 minute. The problem is that it consolidates the logs into 1 instead of making 1 log for each one in the queue.
When it becomes necessary to carry out an audit, it will give me a headache, but that’s what I’m doing so my company doesn’t stop.
Hello @Joao_Cruz
Thank you for bringing this back to our attention. We sincerely apologize for the inconvenience caused by the recurrence of the issue with webhooks.
The problem should now be resolved, as the queues have been processed successfully, and all your records should be processed accordingly. If you continue to experience this, please provide any additional details in the support ticket you created. Our Care Team has the right tools to investigate further if necessary.
Once again, we apologize for any trouble or disruption this has caused.
Thank you so much for your patience and understanding.