Balance and cost errors

Every run in Dubsado Alchemy is priced before it starts. If your balance cannot cover the run, the app stops and tells you exactly why. Nothing is charged when a run is blocked.

The three messages you might see

When generating a Workflow Map, the cost matches the number of services in the map:

"This map covers N services, so it costs N credits. Your balance is X. Add credits or remove a service."

When adding a service to an existing map:

"Adding a service costs 1 credit. Your balance is X."

When requesting a revision after a map's included revisions are used:

"This map's included revisions are used up, so this revision costs 1 credit. Your balance is X."

What to do

The fix is the same in every case. Reload credits from the header, or reduce the scope of the run. For a generation that covers more services than your balance allows, removing a service brings the cost down to match.

These messages are checks, not errors. The run was stopped before anything happened, your balance is untouched, and your intake is exactly as you left it. Once your balance covers the cost, run it again and it proceeds normally.