search

tamaq2048 / slack-summarizer

OpenAI's ChatGPT API to create and post a summary of a Slack public channel.
1 stars 0 forks source link

発生しているエラーを特定し原因を調査する #1

Open tamaq2048 opened 1 year ago

tamaq2048 commented 1 year ago
tamaq2048 commented 1 year ago

https://platform.openai.com/docs/guides/error-codes/python-library-error-types

tamaq2048 commented 1 year ago

ServiceUnavailableError Cause: Issue on our servers. Solution: Retry your request after a brief wait and contact us if the issue persists. Check the status page.

A ServiceUnavailableError indicates that our servers are temporarily unable to handle your request. This could be due to a planned or unplanned maintenance, a system upgrade, or a server failure. These errors can also be returned during periods of high traffic. We apologize for any inconvenience and we are working hard to restore our services as soon as possible.

If you encounter a ServiceUnavailableError, please try the following steps:

Wait a few minutes and retry your request. Sometimes, the issue may be resolved quickly and your request may succeed on the next attempt. Check our status page for any ongoing incidents or maintenance that may affect our services. If there is an active incident, please follow the updates and wait until it is resolved before retrying your request. If the issue persists, check out our persistent errors next steps section.

tamaq2048 commented 1 year ago

Timeout Cause: Request timed out. Solution: Retry your request after a brief wait and contact us if the issue persists.

A Timeout error indicates that your request took too long to complete and our server closed the connection. This could be due to a network issue, a heavy load on our services, or a complex request that requires more processing time. If you encounter a Timeout error, please try the following steps:

Wait a few seconds and retry your request. Sometimes, the network congestion or the load on our services may be reduced and your request may succeed on the second attempt. Check your network settings and make sure you have a stable and fast internet connection. You may need to switch to a different network, use a wired connection, or reduce the number of devices or applications using your bandwidth. If the issue persists, check out our persistent errors next steps section.

tamaq2048 commented 1 year ago

RateLimitError Cause: You have hit your assigned rate limit. Solution: Pace your requests. Read more in our Rate limit guide.

A RateLimitError indicates that you have hit your assigned rate limit. This means that you have sent too many tokens or requests in a given period of time, and our services have temporarily blocked you from sending more. We impose rate limits to ensure fair and efficient use of our resources and to prevent abuse or overload of our services.

If you encounter a RateLimitError, please try the following steps:

Send fewer tokens or requests or slow down. You may need to reduce the frequency or volume of your requests, batch your tokens, or implement exponential backoff. You can read our Rate limit guide for more details. Wait until your rate limit resets (one minute) and retry your request. The error message should give you a sense of your usage rate and permitted usage. You can also check your API usage statistics from your account dashboard.

tamaq2048 commented 1 year ago

APIConnectionError Cause: Issue connecting to our services. Solution: Check your network settings, proxy configuration, SSL certificates, or firewall rules.

An APIConnectionError indicates that your request could not reach our servers or establish a secure connection. This could be due to a network issue, a proxy configuration, an SSL certificate, or a firewall rule. If you encounter an APIConnectionError, please try the following steps:

Check your network settings and make sure you have a stable and fast internet connection. You may need to switch to a different network, use a wired connection, or reduce the number of devices or applications using your bandwidth. Check your proxy configuration and make sure it is compatible with our services. You may need to update your proxy settings, use a different proxy, or bypass the proxy altogether. Check your SSL certificates and make sure they are valid and up-to-date. You may need to install or renew your certificates, use a different certificate authority, or disable SSL verification. Check your firewall rules and make sure they are not blocking or filtering our services. You may need to modify your firewall settings. If appropriate, check that your container has the correct permissions to send and receive traffic. If the issue persists, check out our persistent errors next steps section.