Automation Fan-out Credit Ledger

How to use Automation Fan-out Credit Ledger

One scenario run can fan out into many downstream bundles. Trace that multiplication step by step before estimating a workflow budget.

1. Enter each step once and give it at most one parent.
2. Supply observed bundle factors, credit units and additional-attempt assumptions.
3. Review every row against actual scenario logs and the current billing contract.

Good to know

• An acyclic single-parent graph is required; unknown parents and cycles are refused. Bundles/input≤10,000, extra attempts/bundle≤100. Retry duplication, aggregation, joins, variable payload classes and actual vendor pricing need a separate model.
• Fields are limited to8,000 characters; CSV has at most100 data rows and exact displayed headers. Quoted commas, newlines and doubled quotes are supported. Labels use1–200 characters. Ordinary nonnegative decimals have at most9 fractional places, magnitude999,999,999; whole counts and percentages have stricter displayed limits. No exponent notation. Results outside0.000000000001–1 quadrillion are refused, except zero.
• Independent deterministic ToolJovia workflow. Inputs stay in this browser; no model call, vendor request, saved input, external workflow execution or message sending occurs. Outputs contain your entered records; review them before sharing. A modeled result is not proof of customers, revenue, regulatory compliance or vendor billing.