#Large numbers of 502s

1 messages · Page 1 of 1 (latest)

quaint fox
#

We keep getting 502s at different times and each time we get it the timeout is roughly 10 minutes. It's to the point where this is unusable and we really need a fix.

{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  39000  at controller test  at time:  2023-09-14T07:27:21.270Z
undefined
seconds waiting:  37000  at controller test  at time:  2023-09-14T07:31:23.857Z
{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  57000  at controller test  at time:  2023-09-14T07:42:03.218Z
{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  57000  at controller test  at time:  2023-09-14T07:53:03.918Z
{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  55000  at controller test  at time:  2023-09-14T08:04:05.098Z
{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  49000  at controller test  at time:  2023-09-14T08:15:11.256Z
{
code: 502,
message: 'Bad gateway.',
param: null,
type: 'cf_bad_gateway'
}
seconds waiting:  57000  at controller test  at time:  2023-09-14T08:26:03.531Z

^^ as an example, with retries.

quaint fox
#

does anyone have any idea?

#

we are still facing this issue - this is pretty unacceptable for a paid product

marble goblet
#

You can view the openai status page to check whether the API server is working alright, the TOS is coming soon.