The "status" has to be a number.
Seems like there was some bug in graphql-kotlin since it did not return an error previously and with updating to the latest version it now returns one
Everytime the data was updated, the array changed and triggered the useEffect again, resulting in another request to get the latest data from the tracker
Apollo fails to handle changes in the options context (e.g. abort controller) which causes the request to infinitely re-trigger on errors.
By not adding an abort controller, this gets prevented, however, it prevents the search to be aborted on e.g. changing the search string
