Hi @Shubhanshu_Shukla, @Pankaj
We are making a call to /v0.5/contents/fetch on the gateway as an HIU user. That call is returning a 202. Our HIU server doesn’t receive the callback on /v0.5/contents/on-fetch
POST /v0.5/consents/fetch HTTP/1.1
X-CM-ID: sbx
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2NDc4NTU5NDIsImlhdCI6MTY0Nzg1NTM0MiwianRpIjoiMWVjOGUwMmUtYzEzZC00MDJmLTgxZDItOGU1ZmUzNTQ1M2I3IiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiIxNjEyNTg2Ny01ODZhLTQwZDctYWMwZC1mM2Q3Yzg4YzBlZTkiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJzdW1hc29mdCIsInNlc3Npb25fc3RhdGUiOiI0Yjk4N2NlYy02NWIxLTRlZDgtOGY5OS1iZDQ1N2NiOGViZGIiLCJhY3IiOiIxIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9sb2NhbGhvc3Q6OTAwNyJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiaGl1Iiwib2ZmbGluZV9hY2Nlc3MiLCJoZWFsdGhJZCIsIk9JREMiLCJoZWFsdGhfbG9ja2VyIiwiaGlwIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsic3VtYXNvZnQiOnsicm9sZXMiOlsidW1hX3Byb3RlY3Rpb24iXX0sImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoib3BlbmlkIGVtYWlsIHByb2ZpbGUiLCJjbGllbnRIb3N0IjoiMTAuMjMzLjY4LjEwMCIsImNsaWVudElkIjoic3VtYXNvZnQiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsInByZWZlcnJlZF91c2VybmFtZSI6InNlcnZpY2UtYWNjb3VudC1zdW1hc29mdCIsImNsaWVudEFkZHJlc3MiOiIxMC4yMzMuNjguMTAwIn0.Hg_dvdaqxDbyV73AZd2p4LzXIkk_iIxqvaoilndL8nzqMZbR0_DZ_DvK17qELY4guOTx1w2dpJfpaIPeUNRRh2_50dk2Y4cswcjpTGCIsgdEuncIVNoDdNTApIiG0-w6hrpDwfDwPw4aJxxRGJkmKzZkSXtlIOjKiR42m6GYh2T9nc_3EhrDIjXkdQBnVKJhDWdHZqaBr4Cdz1waPwA1YrUMHsAjltnhHjXr2cJj3BI2ZytChudBtc0W4tBrw-eJ3FYaX8lEfd3EPvKyloaWu9lOYsct6KM2ouyk7CHKQxKdqWCyzD_05Ng6CfYDYpkjVnLTGJ2CJIlhDggZaORA4A
Content-Type: application/json
User-Agent: PostmanRuntime/7.29.0
Accept: /
Postman-Token: 8269affa-605f-4fee-a52a-5236328bc828
Host: nha-suma-azb7fa3pfa-el.a.run.app
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 159
Cookie: TS011c04bd=01115a1c902774c08f7f6418741715f78e3a3ae6a37062808a893f2070ffe7bd4e3060a872e26d17003f8c964bf38e3bfb0815df18; TS01c078b5=01115a1c905d0909a51746da1e3103868f64168c98ff95c1c3656b6856d37147c88975297f1b20cdce21a022e348bb6ba4d78f89d7
{
“requestId”: “ab5ebfa9-e329-4197-98bf-adc5924aed02”,
“timestamp”: “2022-03-22T05:27:13.839Z”,
“consentId”: “d793077b-1c54-415a-8dc1-75f2580b9f8c”
}
HTTP/1.1 500 Internal Server Error
content-type: text/html; charset=utf-8
access-control-allow-origin: *
X-Cloud-Trace-Context: 66620b8ed1289785f090e264c73fa75d
Date: Tue, 22 Mar 2022 05:27:14 GMT
Server: Google Frontend
Content-Length: 290
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v=“46,43”
500 Internal Server ErrorInternal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Loop: @varsha