Flow versions and one-click reruns are live

<p>Two things shipped this morning that people have asked for since the first week of the beta. Flows now keep a version history, and a failed run can be sent through again without rebuilding anything by hand.</p><p>Versions cover the whole configuration: the trigger, the field map, the filters and the schedule. Each save writes an entry with the date and the person who made it, and the last twenty entries stay available for ninety days. Open the history, put two versions side by side, and restore one if a change turned out to be wrong. Restoring does not run the flow, it only puts the configuration back, so you can look before you turn it on again.</p><p>Replays are simpler than they sound. When a run fails because a select option was renamed or an app was briefly unreachable, the run history now carries a Replay button. It reads the source record again, applies the current mapping and writes the result, which means a fix can be tested against the record that actually failed rather than a made-up one. Replays are capped at fifty records per click on Starter and five hundred on Team.</p><p>Neither feature needs a migration. Existing flows began keeping versions at their next save, and runs from the past thirty days can be replayed right now. Anything older cannot, because we stop holding the record payload at thirty days, which is the same retention window described on the security page.</p><p>Next on the list are a bulk edit for field maps and a daily error digest that arrives as one email instead of one message per failure. Both are being tested by about forty accounts and should land before the end of March.</p>