Hello everyone @here 
I just wanted to thank you all for proactively contributing and sharing valuable information about this Webflow issue with the community. Having all this info in one place is a tremendous help for any other folks who encounter this.
Just a quick update from our end: Webflow reached out to acknowledge the existence of this issue and that they are actively working to resolve it. They should notify us once everything is up and running again.
Fingers crossed that it’ll be sorted out soon 
3 Likes
I downloaded the blueprint and then imported it into a new blank scenario. That get’s you the V1 modules. Then open a separate window with your scenario that has the v2 modules. Copy the specific v1 modules from the first window/scenario into your existing set up. That should let you have both versions coexisting so you can simply swap them out or set up a router that has two legs one with v1 versions and a one with v2. In my situation I disabled the leg that has the v2 modules until webflow fixes things. I’ll take an image of what I set up. Hopefully that will help.
3 Likes
Ahh, I was editing the blueprint instead of copying it into Make and doing everything else within their UI. Now it works! Thank you 
3 Likes
One of my automations has a Webflow API v2 update step that just took 24.2s — unacceptable by 50-100x!
1 Like
Hello everybody @here
I am certain that most of you already know all that I’m about to post but the Webflow team reached out to us with this message so I wanted to pass it on.
There is a problem on Webflow’s end with /publish endpoints and there are current restrictions on their side until resolved to enforce API limit for request handling.
This limitation affects the following modules
Publish an ItemPublish a Site
Message from Webflow:
CMS Rate Limits
As many of you have encountered over the past few days, we had to decrease the rate limits on CMS publish endpoints in response to some infrastructure issues on our side. We’re actively working to restore those limits back up to normal and you should see some relief from 429s as we slowly raise those limits.
We also wanted to point out that, while it’s not outlined in the docs yet, those publish endpoints accept an array of 100 CMS item IDs in the itemIds field.
Thank you again for your bug reports, continued support, and patience while we’re working through these issues 
2 Likes
Thank you for the update.
2 Likes
