Flows says which step is wrong now - and stopped offering steps that did nothing

A pass over the flow builder aimed at one thing: making it readable without being taught. The save error that told you nothing is gone. Saving a flow with a half-filled condition answered “String must contain at least 1 character(s)” - technically correct, and useless across a flow with forty steps. It now says “Update record (‘Notify the owner’) - condition 1 has no field chosen”, opens that step, and outlines the exact control in red. The information was always there; the validator knew precisely where the problem was and the message threw it away before it reached you. Activation failures speak the same language, and every problem in the banner has a Show me link. The settings panel is half again as wide, and you can drag it wider. A condition is three parts - field, operator, value - and they were being crushed into a fixed 340 pixels; below a certain width they now wrap to a second line instead of shrinking to stubs. The list of 38 steps no longer sits underneath the step you’re configuring, so setting one up doesn’t mean scrolling past your own settings. Flow cards are cards again - Pause and Edit, with duplicate, rename, export, move and delete behind a menu. Test data now follows your trigger. Every captured sample records which trigger produced it, and the builder was ignoring that: switch from Record created to Form submitted and you carried on mapping fields from a record you would never receive. Samples for other triggers are hidden rather than deleted, so switching back brings them straight back. “Record updated” can now watch specific fields instead of firing on every change - leave it empty and it behaves exactly as before. And deleting a field tells you what it breaks, before you delete it. Which automations, which forms, which lists, each one linked, with the offending step named. Live automations block outright; paused and draft ones warn. Renaming a field has always been safe - the underlying key never changes - and the field editor now shows you that key so anyone writing it by hand uses the right one. Six steps were retired: Send SMS, Send WhatsApp / DM, Publish social post, Update product, Update stock and Do in parallel. Two of them had never had a settings panel at all - you could add them, and they could never be configured, and they silently did nothing. That was found by a new test that checks every step in the palette is wired end to end: a name, a settings panel, something that runs it, and a readable error when it isn’t finished. A flow that already contains a retired step still opens, still saves, and still runs everything around it - the step itself is marked in red as removed, with a delete button, rather than vanishing quietly. Social posting, WhatsApp and SMS all remain available where they belong; it is only the automation steps that are gone.