What if a Webflow change broke a different block?

Keep the change you asked for

A side effect is a new problem on a block the request did not name. The change you did ask for can stay. This note is how you report the new problem without throwing out work that is already right.

The undo guide is the other case. Use it when the live page should go back to the earlier version. Use this page when the new version should remain, and a different block needs a repair.

Example: you asked for the first paragraph on /services to use the approved sentence. That sentence is now on the live page, and it matches the file you sent. On a phone, the button under that paragraph sits on top of the words. You want the sentence to stay. You want the overlap fixed.

Name the block that should stay

Start in the same thread as the original request. Write the live URL a visitor would open. Then name the block that is correct, and paste the part that should remain, so there is no guess about which version you mean.

'Keep the new first paragraph on /services. It matches the approved file.' That line stops the repair from becoming an undo. If you only write that the services page looks wrong, the requested sentence can be removed along with the overlap.

If you are no longer sure the new paragraph is the one you approved, say that in the same note and attach the file again. Do not ask for a guess about which sentence belongs there. A picture can point at the block. The sentences still have to stand if the picture is missing.

Name the block that broke

The second part of the note is the new problem. Name the block, say what you expected, and say what you see instead. Someone who was not watching the page should be able to find it from the note alone.

'On a phone, the button under that paragraph covers the last line. It should sit below the paragraph, and it should still open /contact.' That is a repair. A note that says the spacing feels off is not, because it does not name the button or the width.

Write the width you used. A desktop check does not answer a problem that only shows on a phone. If a second block also broke, list it in this same note. A later message that only says the footer is wrong is easy to miss, and it can be treated as a separate request.

Say what must not change. The headline, the other sections, and any page you did not name should stay as they are. A repair that restyles the whole services page is a different request. The problem guide is the shape of a first report. This page adds the line that protects the change you still want.

Leave a full undo for a different decision

Do not start this note by asking for the whole page to go back, and do not start it by asking for a full site restore. A backup restore is a whole-site action. It is the wrong first step for one button on one page. Ask for the named block to be repaired, with the approved paragraph left in place.

Ask for an undo only when you have decided the requested change should be removed too. Say that in writing, and paste the version that should return. Hours already spent on the original change stay spent. If the repair would pass the hours that are left, additional work starts only after you approve a written estimate. Sending the repair note is not that approval.

If two open notes now describe /services, name which one to build and which line to ignore. Silence does not pick a winner. The repair should be the only active instruction for that button.

Send the repair in the same thread

Reply in the thread that already holds the original request. A new thread can look like a second job, and the result you wanted to keep can be undone by mistake. Communication is asynchronous and written only. There are no calls or meetings.

Mark the note urgent only when visitors are blocked from something they need and you want the 24 hour review. Any other request is reviewed and picked up within 48 hours. Those windows are pickup times, not a promise that the button will already be fixed inside that window.

The Webflow retainer is the monthly plan this repair belongs to: $999 per month, including 10 hours of Webflow work. Additional work is $75 per hour. Unused hours expire at the end of each monthly billing period and do not carry over. The retainer guide explains which ongoing work those hours cover. Use this page when a change you asked for is right, and a different block is not.