Aaaaand the pricing page states 120 
2 Likes
I am also upset. Not that this happened. I’ve been in tech for a long time and I know things break. But the response from Webflow has been disheartening to say the least.
It took 36 hours to receive a non-answer to my support request and each answer since has been a canned, corporate copy paste style “we’re sorry, we’re looking into it, etc.” response that somehow fills an entire email with words without actually saying anything at all.
It has been 5 days with no fix. This should be treated as a hair-on-fire people’s-sites-are-down problem and yet it feels like Webflow doesn’t care. I spent three months of my life building a Webflow site and my anger is coming from the fact that I now feel locked into a service that doesn’t care enough about the fact that their mistakes are hurting my business reputation to even send a real update.
3 Likes
This is extremely painful.
2 Likes
It took 10+ hours but remaking all my scenarios in Make with the v1 blueprint above worked for me. Import the blueprint into a new scenario, copy the v1 module you need and paste it into your broken v2 scenario, add a router to create a new path, disable the old path, then clone all the other modules and recreate the scenario with v1. I found this actually better because the v1 modules allow you to create and edit live items so you don’t have to separate out creating, updating, and publishing. If/when v2 works you can just change the router to go back to what you had before.
2 Likes
Same - just 2 issues:
- The v1 API has gotten incredibly slow for me, about 10x slower than it was before v2
- Soon enough, it will be deprecated. The Webflow team says it will still be active until the end of 2024 I believe, but I can’t help but feel it will get slower and slower until then, becoming completely useless along the way.
I am praying for this to be fixed with the v2 API as soon as possible - along with that, I’m hoping for some sort of PAYG option for the API - that would make it a lot more scaleable.
1 Like
I’m noticing another issue. When I went back to v1, any live item that is published, is updated in webflow and says published, but is not updated on a live site. I have to manually publish entire website to see changes. Anyone experiencing the same?
1 Like
I am encountering this same issue which is a huge bummer because using the API was making some functions so much easier. I have emailed Webflow to let them know I am encountering this issue as well.
2 Likes
Hello everyone,
On make.com we can also use API 1.0.0 as indicated in @Julian_Galluzzo’s email. All you need to do is make an HTTP request instead of using the pre-made webflow module.
This requires a few changes, but you can create elements with the “live” value. But it works, I tested it with the documentation and it directly published my new item.
I hope this gets you unstuck, and if necessary I’ll do a demo.
1 Like
I will give it a try. But this does not make any sense.
not sure what kind of relief we will get cause I’m still seeing the 429 errors 
3 Likes
I got 429 problems and Webflow is one 
1 Like
3 Likes
Anyone heard anything other than “You should see some relief”?
I have heard they restored it to 20 and plan to restore the standard limits in a few days - I am really hoping they also allow some sort of tiered option for rate limits too so people can scale from business to enterprise hosting (theres a big gap between $45 and $10,000 which is currently unserved)
2 Likes
But what is the rule here? So, do I need to prepare all the Items and then publish all of them at the same time? And the limit is 100?
[solved]
The temporary rate limits on this endpoint have now been fully lifted and restored to their default values 
Background
I can confirm that our team had to temporarily adjust the rate limits for this endpoint specifically as a necessary measure. Thankfully, the team made great progress to restore this to its original value – and have restored the rate limits from its temporary reduction of 5RPM.
Rest assured that our teams did not take this action lightly, and completely understand the impact this may have had on your workflows — we apologize for any inconvenience that this has caused but are thrilled to report that this has been solved.
4 Likes