Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My Make credits or operations run out too fast

Short answer

Make counts usage per operation, and for most apps one operation equals one credit; AI modules and some apps can use more depending on tokens, file size or run time. The usual culprits are scenarios that run too often, iterators that multiply bundles and retries after errors.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Credits are gone halfway through the billing period.
  • I do not know which scenario uses the most.
  • A scenario that runs every few minutes does little useful work.
  • A list of 200 items turned into hundreds of operations.
  • Make suggests I buy extra credits.

Why does this happen?

  1. One operation is one credit for most apps

    Make states that for non-AI apps one operation equals one credit. Credits track spending and operations show the outcome of your activity.

  2. AI and file modules can cost more

    Make states that some apps use a fixed number of credits per run, and others use dynamic credits based on tokens, file size, pages processed or run time. AI modules can cost more than one credit per operation.

  3. Iterators multiply operations

    An iterator turns a list into one bundle per element, and every module after it runs once per bundle. A scenario that handles a list of items spends operations for each item at every step.

  4. Frequent schedules and failing runs

    A scenario that checks every few minutes spends operations even when there is nothing to do, and repeated failing runs spend them again.

What can I do about it today?

  1. Open usage by scenarioFind the top three scenarios and write down how often each runs.
  2. Compare runs to real eventsIf a scenario runs 500 times a day for 20 real orders, the schedule is too tight.
  3. Look for loops over listsA scenario that handles list items one by one is a common cost.
  4. Do not switch scenarios off blindlySome carry payments or notifications. Ask who relies on each one.
  5. Read the running-out optionsMake says you can upgrade, buy extra credits or enable auto-purchase of extra credits. Decide if buying is the right answer first.

When should I bring someone in?

  • Credits run out before the end of every period.
  • You are about to upgrade without knowing why usage is high.
  • The scenarios handle money or customer messages.

How do I handle it?

  1. Measure per scenarioI rank scenarios by credits per run and runs per day.
  2. Remove wasteSchedules are loosened, filters are put near the start and lists are handled in batches where the app allows.
  3. Check error loopsFailing scenarios that retry endlessly are fixed so they stop spending.
  4. Decide per flowEach scenario is kept, simplified or moved elsewhere, with the reason written down.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

What happens when credits run out?

Make's page lists what you can do: upgrade, buy extra credits or enable auto-purchase. It does not describe what happens to scenarios if you do none of these.

Are credits and operations the same?

Make says they are separate terms: credits track spending, operations show the outcome of your activity.

Will fewer operations change my results?

Only if a step is removed. Each change is checked against what the scenario is for.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.