How/why is "Deleted Search" driving so much workload usage?

I was clicking through my App Metrics, and noticed that a surprising % of workload usage this month is attributed to “Deleted Search.” This entry isn’t clickable, so it’s not possible to see the related element, condition or workflow.

Can someone define what exactly “Deleted Search” is? Then hopefully suggest how I can debug, and drive this number down?

Likely this could be because of a known bug. Please submit a bug report to Bubble about it.

Ack, and submitted to Bubble.

1 Like

One thing to note, if you are still experiencing WU consumption in relation to this ‘deleted search’ after it was initially deleted, it may be because of the bug. But, if you are seeing it for metrics that were from prior to the deletion, then ‘deleted search’ is just a reference to the search itself. I don’t know why Bubble wouldn’t append to the name ‘deleted’ as it makes it very confusing and hard to pin down since it is easier to understand ‘deleted - search for products’ rather than just ‘deleted search’.

What is even weirder and more annoying, is that if you deleted the search, then used the ‘undo button’ in the editor to get the search back. The metrics for past WU usage that occurred before the deletion will show as ‘deleted search’ instead of referencing the search by name, even though it was added back via the ‘undo button’.

Little details like that will hopefully be improved upon by Bubble.

1 Like