cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

GraphQL stuck when running in App (runs fine in playground)

I am working on a web ui that is primarily an interactive map. I am applying filters to narrow results for the query. When running the query in the playground it runs quickly and easily. However, sometimes the query gets "locked" when it runs in the application. I have an inkling it might be due to how some map markers are being rendered; however, in the past the query has run just fine, and then sometimes locks up. So the performance seems a bit inconsistent.

Has anyone else had an issue like this?

1 ACCEPTED SOLUTION

I figured out that i was using a slightly varied version of the query between the application and the playground. When I used the query from the playground in the app, the "locking up" went away.

View solution in original post

3 REPLIES 3

William_Lyon
Graph Fellow

Can you share some code to show how the query data is being used? Specifically, this is probably the children props of the Query component.

I figured out that i was using a slightly varied version of the query between the application and the playground. When I used the query from the playground in the app, the "locking up" went away.

This was tied to exploring the implementation of nested filters.