Follow-up on today’s issues

Hi all,

The team has made a change to temporarily prevent very large branches from merging. It was causing platform stability issues. If you experience this issue, you will see an error message in the editor. We expect to lift this block by Thursday, May 23, and will post an update about this situation tomorrow.

@josh is also aiming to make a new platform stability post this coming Friday to act as a follow-up to the one he posted last Friday. We know how impactful these outages are, so we’re increasing the cadence of updates to be as transparent as possible with everyone.

10 Likes

Does this affect dedicated plans?

It does not

3 Likes

Pre warning us before making drastic changes so we know to expect issues before it happens. This is the way. <3

7 Likes

Thank you @fede.bubble.

We realize you’re in a tough spot but we appreciate any communications and transparency you can provide. :pray:t4:

I get that you’re doing your best but I’m right in the middle of a massive user test planned for weeks and these people have carved out time for us. I can’t just “move it and wait”. We’re fixing the issues that are coming up so they can test again and our go live is at the end of next week. We NEED to merge. What can we do?

3 Likes

Thanks for the update!

Wait until may 23

In addition to being unable to merge is any one else getting this rate limiting message?

The lack of a heads up is great we will just tell our investors and users not to worry the platform that we are using to build on is unstable and we anticipate it will become stable again later this week.

1 Like

I can ask around, but honestly this is probably better answered via support. They can look at your app records, etc and better troubleshoot

Haven’t got that one so far.

UPDATE

All, the team has re-enabled large merges today (instead of tomorrow Thursday as the original update says)

6 Likes

Today’s current issue is that branch merges altogether are not working (for myself at least - a custom branch into Main.) Already filed in ticket in support via the Intercom chat.