Skip to main content

Why does the same workflow sometimes use different amounts of Workload Units?

The same workflow action can cost different amounts of WUs depending on whether cached data is available. This is expected behavior — caching makes most runs cheaper than the documented cost.

Written by Sofia Maconi

Running the same workflow action can cost different amounts of Workload Units (WUs) at different times. This is because Bubble caches many operations behind the scenes — when cached data is available, a workflow runs faster and uses fewer WUs. Occasionally the cache needs refreshing, and when that happens the same workflow runs without cached data and costs slightly more.

What you might notice

  • The same workflow action shows different WU costs at different times

  • A workflow action you expect to cost a certain amount occasionally costs more

Workaround

No action is needed — this is expected behavior and works in your favor. The WU costs published in Bubble's documentation represent the non-cached (higher) cost. In practice, most workflow runs use cached data and cost less than the documented amount.

Did this answer your question?