Something went wrong while executing your query C7D2:390D:1412CC3:18B7FA1:5C4E105A #24408
-
The query I’ve using has been working for a long while now and recently it stoped working. The most relevant portion reads:
Full error message:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
Hey @givanse! Do you have a copy of the query, by any chance? Looking at the error on our end, it appears that your query timed out - this can happen when a user is requesting a significant amount of data, especially when maximizing their connections and asking for 100 resources at a time. If possible, I would recommend cutting down on the number of resources you are requesting at once, and doing more overall queries. This will allow each one to fit into the allowed time, and hopefully result in more successful queries! |
Beta Was this translation helpful? Give feedback.
-
Thanks for confirming that it is a timeout! After reading your reply I realized that: - it is a dynamically generated query, and - the number of repos/orgs (in my data set) must have increased enought to push it over the limit case solved, I’ll split my query |
Beta Was this translation helpful? Give feedback.
-
Thanks, @givanse for coming back and providing feedback on what worked! We’re looking forward to seeing you around! |
Beta Was this translation helpful? Give feedback.
-
@nickvanw I’ve tried cutting down on the number of resources I’m requesting at once, and I’m still getting this error. To be fair, the repo I’m trying to pull from has ~150,000 pull requests. I see your other suggestion is to do more overall queries. How would I go about doing that? For reference, this is what my query looks like:
|
Beta Was this translation helpful? Give feedback.
Hey @givanse!
Do you have a copy of the query, by any chance?
Looking at the error on our end, it appears that your query timed out - this can happen when a user is requesting a significant amount of data, especially when maximizing their connections and asking for 100 resources at a time.
If possible, I would recommend cutting down on the number of resources you are requesting at once, and doing more overall queries. This will allow each one to fit into the allowed time, and hopefully result in more successful queries!