> ## Content Index
> Fetch the complete content index at: https://www.waterboy.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# A pretty reliable way to handle concurrency in bubble.io and save WU
- URL: https://www.waterboy.tech/a-pretty-reliable-way-to-handle-concurrency-in-bubble-io-and-save-wu/
- Published: 2026-09-28T16:06:15.000Z
- Updated: 2026-09-28T16:06:15.000Z
- Author: waterboy

btw I could be wrong; open to suggestions and alternate methods.

One of Bubble's biggest flaws is handling concurrency.

Say for example you have to display reporting data for sales. 

Current sales: $100.

When 2 simultaneous orders are placed, both read 100 and update it at the same time.

So the values from 1 order get missed.

Solution(this solution also helps you save workload units. Esp for for datatypes with 100k+ records)

**Step 1**

Have an aggregate datatype.

Eg ReportingDaily(Field - Total Sales: 100, Date label: Date Text)

Every time an order is placed, create a "NEW" thing in the table. 

Whenever you are displaying your sales, do a sum of all the Reporting Daily's > Total Sales.

**Step 2** 

Set a common daily recurring wf that runs at a certain time. 

Preferably when there is less activity.

At this time, roll up the entries of the previous day.

Rollup means taking all the entries for the date label of the previous day and SUM them. 

Then delete the other entries. This should leave you with 1 entry for that day.

So if you have about 10k orders on that day, you only need to look at 1 entry.

This is missing a lot of the nitty-gritty stuff, but that you can figure out.

Hope this helps.