Instant triggers stopped working yesterday, they work very inconsistently sometimes they work and then randomly a few seconds later they don’t work for 20-30 minutes, even some of my scheduled runs didn’t run yesterday, I had to run them manually an hour late…
Welcome to the Make community!
For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your account or scenario might not be suitable for an open forum discussion.
You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users). After submitting a new ticket, you will receive an automatic confirmation email with the subject “Ticket Created” in the subject. If you do not receive this, try sending the ticket again.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
Not sure why you keep welcoming me to the community, but thanks. This is not a user specific situation, as multiple scenarios are working one moment and then not working the other. Scenarios that have been up and working for over 2 years now 24/7. This is basically a “is Make down?” topic, as the status page doesn’t seem to show any downtime.
Edit: I’ve been manually triggering automatic triggers throughout the whole day today and yesterday (WhatsApp, GitHub, and more) whilst the same scenarios also triggered as intended a couple of times today.
Hey Marcel1
Sounds frustrating.
In your scenarion, is any errors returned in the logs, when they stop working?
- Thought here; If it stops and there is no error, the it’s time to get a hold on support as @samliew said.
How many time and how often does data get send to this weebhook(s)?
- Thought here; Is the queue full?
Nothing stops, no errors. The scenarios do not get triggered, or like 20-30 minutes later (when the trigger should be instant, or even scheduled for example it’s scheduled to run at 3 pm but then doesn’t). As I’ve said, these scenarios have been up and running for more than 2 years now and it’s never happened before like this, and even now it’s very inconsistent because when it triggers late after 20-30 minutes it happens that the next data immediately triggers as it should. It feels like there’s downtime somewhere, as that would explain this behaviour but I don’t see any downtime on the status pages.
It says 1-2 webhooks in queue waiting to be processed, which also answers your second question there’s never more than 1-2 webhooks in queue at the same time and data gets sent a couple times a day depending on the day, but it’s always spread out.
Today everything has been working as it should so far, so I’ll keep a close eye on it for now. Hopefully whatever it was resolved itself…
Hey Marcel
That is annoying for sure.
With the feedback you just gave, I would contact support, see if they can spot something backend.
It does not sound as if, this is something that we would be able to troubleshoot and/or fix.
Hope your watchful endavour, will discurrage the scenario to play games with you.
Best of luck.