When you have a forward proxy server that is part of the SAS infrastructure deployment, IFRS17 cycles run randomly, and the cycles fail with the following error:
MPRINT(IRM_REST_REQUEST): proc http url =
"https://<hostname>:443/SASRiskGovernanceFramework/rest/rmc/cycles/61197?&ticket=ST-2919-AbmRIR-iiYuJhIH10ecHHqL-O58-
frdevsaw27" method = "PATCH" headerin = patchHin in = cycleBdy headerout = __hout_ out = __out__ ct = "application/json"
clear_cache ;
[...]
> PATCH /SASRiskGovernanceFramework/rest/rmc/cycles/61197?&ticket=ST-2919-AbmRIR-iiYuJhIH10ecHHqL-O58-frdevsaw27 HTTP/1.1
[...]
< HTTP/1.1 502 Proxy Error
[...]
NOTE: 502 Bad Gateway
NOTE: PROCEDURE HTTP used
To circumvent this issue, implement or append the following parameter within the Apache Server sas.conf file:
SetEnv proxy-initial-not-pooled 1
ProxyRequests off