502 Bad Gateway

Dear Team,
We received a 502 Bad Gateway error. Specifically, on 23rd January 2025, 42 invoices failed to process due to this issue.

Please advise on how we should handle these invoices, preferably without making any modifications to the invoice data.

Looking forward to your guidance.

@Ankit_Tiwari @kiaziz – please provide your inputs.

Response we receive:

{
“headers”: {
“Cache-Control”: “no-store, max-age=0”,
“Connection”: “Keep-Alive”,
“Content-Security-Policy”: “default-src ‘none’; script-src ‘self’; connect-src ‘self’; img-src ‘self’; style-src ‘self’; frame-ancestors ‘none’; form-action ‘self’”,
“Content-Type”: “text/html”,
“Date”: “Thu, 23 Jan 2025 10:57:17 GMT”,
“Set-Cookie”: “TS0106293e=0132a679c0c235c86ef07dcb65708ee6b37731132be6dcbd22e84b5ecad010fcf3b62f5fff54858cbecbb9aeafe716affb0e34ee30; Path=/; Domain=.gw-fatoora.zatca.gov.sa”,
“Strict-Transport-Security”: “max-age=15724800; includeSubDomains”,
“Transfer-Encoding”: “chunked”,
“X-Content-Type-Options”: “nosniff”,
“X-Frame-Options”: “DENY”,
“X-Global-Transaction-ID”: “c7558bdf67922083df2dbe3f”,
“X-Xss-Protection”: “1; mode=block”
},
“result”: “\r\n502 Bad Gateway\r\n\r\n

502 Bad Gateway

\r\n
nginx\r\n\r\n\r\n”,
“httpCode”: 502
}