Getting too much of a workload when retrieving large number of data in backend workflow

[superman38dream]

I am getting too much of workloads when retrieving large number of data in backend workflow. Please let me know how can i optimize workflow.

Please take a look images that shows my current problem.

Thank you.

[ademiguel]

Two potential causes

1. You are performing nested searches which can duplicate the WUs spent. You can try performing those Search for Ticket_status and Search for Users in a previous action, e.g. a Make changes to a thing action, and then refer those results. Otherwise you can be performing that Search once per each Ticket record.
2. The number of returned Ticket records is very high. You are charged WUs per returned items, so this matters. You can try placing more restrictive constrains so the backend returns less records, e.g. a creation date range.

[will_ericksson]

@ademiguel

You are performing nested searches which can duplicate the WUs spent. You can try performing those Search for Ticket_status and Search for Users in a previous action, e.g. a Make changes to a thing action, and then refer those results. Otherwise you can be performing that Search once per each Ticket record.

This is this issue. For every search in the outer search (Tickets) , you are doing two internal searches (Ticket Status and User). So if you return 1,000 results in the outer search, you are adding another 2,000 searches. Youch!

You need to refactor your data structure to hold the Ticket Status and the User on the Ticket. This leverages the relational aspect of the Bubble database.

Then this whole API call will probably use up about 1/2000th of the cost and time.