WU being attributed to a Deleted Search

I deleted a Search over 24 hours ago and thousands of WUs continue to be attributed to it. The Search was in a conditional where the data source was being changed to “do a search for” that I’ve since deleted (or at least the logs pointed me to that conditional). Does anyone understand why this is happening? Is it possible that it wasn’t just the conditional but the entire Search? I should also add that I launched my app two days ago and have already burned through 235K WUs. This seems insane.

It is the entire search that’s consuming the WU’s.
If your User experience would accept pagination, then implement it to reduce WU usage.
Implement constraints where needed.

Thanks for the advice @rakshitkumar90! That’s really frustrating, and deceiving, because when I click on the log it doesn’t send me anywhere (like it typically would send you to the related activity), leading me to believe the search that was using the WUs no longer exists., and it also misrepresents where the consumption is coming from.

If it is in fact the entire search, any suggestions for optimizing a filtering scenario like this? Where I have one repeating group that can be filtered with each of these inputs, each one their own conditional that changes the data source, and all inputs layer?

Instead of changing data source for each filter, add constraints to the same data source & check “ignore empty constraints”.
Make sure the repeatingroup is not showing all data as once.
Lastly add pagination, to call more data only when next page number is clicked.

Pagination will optimise WU significantly since users will depend on filters instead of endlessly scrolling, costing you WU’s.

Is this image showing after you deleted the search or does it include a time where the search was still active?

This topic was automatically closed after 14 days. New replies are no longer allowed.