What are you trying to achieve?
Goal: I would like to log in and see my scenarios.
Steps taken so far
Things I’ve tried: Clearing cache/cookies, logging out/back in, refreshing page, hard refreshing page, yelling obscenities, checking system status.
tracert to us1.make.com gets several “Request timed out” lines.
The Dev console shows just a whole load of errors and API failures on page load.
I’m getting a red box with “OK” and an “x” to click, but no actual message.
A few times, I got into a scenario and a scenario with 2 modules got a “payload too large” error message.
Screenshots: scenario setup, module configuration, errors
Same here, I have been unable to work on Make for over 30 minutes … status.make.com says everything is fine 
I second this. I just cancelled a client call because Make, the “great” platform that I suggested they use to run their business, wouldn’t load. We had the same problem the previous time we met 2 weeks ago.
For the last 2+ months, Make has not behaved as expected.
I have had webhooks that don’t run on demand, and some webhooks that don’t work at all.
I have had missing modules…
And I’ve had scenarios and scenario history that just won’t load in a reasonable amount of time.
Is there any end in sight for this? Is anyone working on these issues?
The status page says everything is OK…when it’s clearly not.
Can we go back to Integromat?
1 Like
While it is great that you are posting on the forum for visibility, support also needs to be contacted to be aware of the issues we are facing.
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). Alternatively, you should be able to send an email to helpdesk@make.com and support@make.com and it should create a ticket. 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.
Join the Make Fans Discord server to chat with other makers!
Hello everyone,
I wanted to quickly step in and apologize for the disruptions and frustration caused by this issue. Our engineering team addressed the situation as promptly as they could. Since then, we have been monitoring the situation, and it has remained stable.
Please know that the stability of our platform and the user experience are extremely important to us. However, we recognize that we have recently experienced multiple performance issues and incidents affecting the US1 zone. We understand the inconvenience this has caused and appreciate your patience as we work to resolve these issues.
Thank you very much for your patience and understanding! 
Your replies here in the community are always so very helpful.
I do not have the time or inclination to submit a ticket for every issue I have encountered in the last 3 months. Especially when users in a Make community I am in are experiencing the same issues.
My hope is that Make is aware of these issues, since they seem to be global and are affecting many users, and will someday fix them.
My post and frustration was due to the length of time these issues have persisted.
I am also privy to information that says the Make engineering team is struggling to keep ahead of the demand of users. Therefore, I know the support team is aware of these issues.
I want to know what the plan is to resolve the performance issues we’ve seen with Make over the last 2-3 months.
2 Likes
The support workflow is in desperate need of update and rethink.
I originally went to that link and figured “technical challenge” may be the right place to go.
“Cannot connect/Server Error/API error” is not an option.
So I went to “My Make Account & Affiliate” instead.
Did you know that it’s inconceivable that someone would have a question regarding their account that is not on this list? That must be why they didn’t include “other” or a text box.
So I went back to the main menu to find another option that would lead me to “cannot log in”/“cannot access scenario” or something similar. It wasn’t there.
So I went back to technical challenge, clicked “I don’t see an error”, followed by “I don’t have a scenario yet”, and ended up on a form that required me to input what modules I was using on the scenario that doesn’t exist and isn’t in question, followed by a “scenario idea” which is irrelevant and required, and then attachments and comments.
I didn’t send this to support because after 20 minutes of trying to figure out where this urgent issue should go, it became apparent that support hadn’t considered this would ever be an issue and I was just plain getting frustrated with how bad that support workflow is.
An active thread with angry people unable to get their work done seemed more effective.
1 Like
@Michaela, with all due respect, I appreciate the response to yesterday’s outage.
A more prompt response on the status page would be great, but thankfully the outage was short.
However, what remains are the glitches and bugs and latency that have plagued Make for the past few months.
- Scenarios that take minutes to load
- Scenario history records that take minutes to load
- Scenarios that hang up and don’t finish in the browser, but have run and finished in the background
- Webhooks that don’t run on demand
- Missing module images
These are just a few items off the top of my head.
These are issues that persist even when Make is “up.”
1 Like
100%! I have yet to submit a support ticket with a category that feels right 
@Samliew, I found your response to be rather condescending and not particularly helpful.
Typically, support replies take 24 hours or more. During the recent US server outage, the status page indicated “Nothing to see here,” which was misleading. It’s crucial for Make to promptly notify users of such issues, especially if their automated monitoring doesn’t catch it.
Many of us depend on Make for our livelihood, and we are well-versed in how to submit a ticket.
Additionally, while your contributions are generally valuable, some of your snippets have felt irrelevant or tone-deaf, which diminishes the enjoyment of your otherwise excellent content.
Hello everyone and thank you all for sharing your thoughts with us, we truly appreciate it.
@andyoneil thank you very much for being super specific with your feedback. We understand that this has been frustrating and please know that we are working on improving the situation as soon as possible.
@James_Campbell thank you for the feedback regarding the support flow. If a similar situation occurs in the future, please select Technical Challenge > I see an error > The error is somewhere else, which is a category intended for situations like these. If any further categorization is unclear, just let us know and we will make sure to answer any questions.
@loic.wiseflow thank you for stepping in and sharing your thoughts. We understand that this has been causing frustration and we are deeply sorry. We also understand that you would appreciate more prompt status page updates and we will do what we can to improve in that respect.
Finally, I am certain that @samliew intended to be helpful rather than condescending. While many community members are seasoned Make users who know who to reach out to when technical issues arise, let’s please keep in mind that there are also new users who do not know how to behave in situations like these. The main message is that while you are welcome to report technical issues in the community, the support team has the right processes to investigate and potentially escalate issues to the developers. It is therefore more effective to let them know first if something goes wrong.
To conclude, I would like to once again thank you all for sharing your perspectives and for being understanding and patient with us as we work to implement improvements.
