How the revision allowance works

Each Workflow Map includes three revisions. They are part of the map, not a separate purchase, and they cover most of the structural adjustment a map needs after generation.

The counter

The action row shows where you stand. It reads "0 of 3 included revisions used" and advances with each revision. When the next revision is the paid one, the button itself changes to read "Revise map (1 credit)", so the cost is visible before you commit.

After the included three

The fourth revision costs one credit and opens the next three. The pattern repeats from there, so paid revisions land on the fourth, seventh, tenth, and so on. In practice: one credit buys another full set of three whenever a map needs deeper rework.

If you attempt the paid revision without enough credits, the message explains the situation: this map's included revisions are used up, so this revision costs 1 credit, followed by your current balance.

On a trial account

On an account that has only the free signup credit, revisions are not open yet. The action row reads "Revisions come with purchased credits." Your first purchase opens revisions, including on the trial map, retroactively.

What the allowance counts against

Revisions count against the original Workflow Map, even when you are revising a revision. The allowance belongs to the map, not to each version of it.

Adding a service is different. It produces a new map with its own fresh allowance of three.

Failed revisions are not charged. If a revision does not complete, nothing is deducted.

How long revisions are kept

Each map keeps its three most recent revisions. Older revisions may be removed. The current map is never affected, and an export of any version is yours to keep. If a past revision holds content you want long term, export it while it is in the history.