[Global]: search api call causes instances api service to crash

[geodem127]

RCA:

The search API was configured with an excessively high result limit (10,000) and no search term. This caused the request to fetch an unmanageably large dataset on page load, leading to frequent timeouts and failed responses.

FIX:

• Removed the automatic API call on page load.
• Implemented a debounced search that only triggers on valid user input.
• Added sensible pagination/default limits to all search requests.
• Refactored the logic to leverage the Redux store for efficient state management.

Loom.Message.-.7.November.2025.mp4

[finnar-bin]

@geodem127 is there any reason why the base branch has been changed? There's currently 300+ changed files

[geodem127]

@geodem127 is there any reason why the base branch has been changed? There's currently 300+ changed files

I'm not sure what happened, but I’ve already switched it back to dev.

[shrunyan]

Why is there so much code changed in the PR when the core of it, as descibed, is going from 10000 to 1000? i.e. I'm expecting a single line change PR.

no default search term.

Also not sure what that means. Why would search have a default term? How would we know what a baseline default term is that meets a users expectations.

[geodem127]

Why is there so much code changed in the PR when the core of it, as descibed, is going from 10000 to 1000? i.e. I'm expecting a single line change PR.

no default search term.

Also not sure what that means. Why would search have a default term? How would we know what a baseline default term is that meets a users expectations.

The other modifications (debounce, filtering block items, and the UI icon) were initially part of the PR but have since been removed. The diff now primarily shows the core architectural change from RTK Query to Redux dispatch.

Just to clarify the RCA description: "no default search term" was a typo. It should read "no search term specified"