Automation Task Quota Scenarios

How to use Automation Task Quota Scenarios

Task allowances depend on which steps run and which events are billed. Separate upstream work, filter pass rates and retry assumptions before selecting a plan.

1. Choose one report period and list nonoverlapping flows and run counts.
2. Declare billed tasks around the filter and the observed pass and retry rates.
3. Enter the period quota and checked excess-task rate, then compare retry-billing scenarios.

Good to know

• At most1,000,000 runs per flow and10,000 whole tasks per side of its filter; percentages0–100. Leave an unknown excess-task unit price blank; only enter0 when a checked rate is genuinely free. Missing price keeps monetary overage unestimated even when excess-task units are zero. This is a task-quota model, not a vendor plan recommendation or topology simulator.
• 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.