Currently, we do not limit the amount of nesting in our graphQl queries, which can result in long running queries.

Things to keep in mind:

1. Find the limiting depth such that a balance is maintained between limiting nesting depth and maintaining query flexibility.
2. Keep the Client Experience in mind. Deeply nested queries can provide more granular data, but they may also make the client code more complex.
3. Make sure to test the GraphQL queries, both within the nesting limit and at the limit's boundaries. Monitor query performance and resource usage to identify any bottlenecks or issues that may arise from the imposed nesting limit.