Skip to content

Commit 4424115

Browse files
authored
Update rate-limits-and-node-limits-for-the-graphql-api.md (#54327)
1 parent 4ef8c73 commit 4424115

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

content/graphql/overview/rate-limits-and-node-limits-for-the-graphql-api.md

+8
Original file line numberDiff line numberDiff line change
@@ -278,4 +278,12 @@ You should also subscribe to webhook events instead of polling the API for data.
278278

279279
You can also stream the audit log in order to view API requests. This can help you troubleshoot integrations that are exceeding the rate limit. For more information, see [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
280280

281+
## Timeouts
282+
283+
If {% data variables.product.github %} takes more than 10 seconds to process an API request, {% data variables.product.github %} will terminate the request and you will receive a timeout response and a message reporting that "We couldn't respond to your request in time".
284+
285+
{% data variables.product.github %} reserves the right to change the timeout window to protect the speed and reliability of the API.
286+
287+
You can check the status of the GraphQL API at [githubstatus.com](https://www.githubstatus.com/) to determine whether the timeout is due to a problem with the API. You can also try to simplify your request or try your request later. For example, if you are requesting a large number of objects in a single request, you can try requesting fewer objects split over multiple queries.
288+
281289
{% endif %}

0 commit comments

Comments
 (0)