Changing your mind

Changing your mind is the normal way to use this, not an exception it recovers from.

Interrupt a running build#

Type and send. You do not have to wait. The message is picked up and the builder carries on with it in mind.

Use this when you can already see it is going the wrong way:

Stop — I meant one page per client, not one page per proposal.

Stop it#

The send button becomes Stop while a build is running. Pressing it ends the run.

Nothing is thrown away. What was finished is committed and saved as a version, and the next message carries on from there. Stopping is safe; it is not an abort.

Correct a misunderstanding#

Say what it got wrong, in a sentence. The whole conversation is still in context, so you do not have to restate the original request.

No — "owner" is the salesperson who owns the proposal, not the person who created the record. They are usually different.

Undo something#

Three ways, roughly in order of how much you want gone.

Ask for it back. Best for a small change.

Put the value column back where it was, before the last change.

Go back to a version. Best when a build made several changes and you want all of them gone. Every build is a version, and you can restore one. See Going back.

Leave it and move on. If it is deployed nowhere, nothing has reached anybody. The preview is yours to be wrong in.

Change the design system#

Not a rebuild. Change how it looks… in the application menu restyles the application in seconds — the colours, the type and the shapes are re-rendered, and no build is spent.

If the new design system has a genuinely different page architecture, the workbench will offer Restyle, which does run a build to rearrange the screens. That one is never automatic.

Start again#

If an application has gone somewhere you do not want, deleting it and creating a new one with a better brief is a perfectly reasonable move — and often faster than talking one back into shape. Applications are cheap here. That is most of the point.