I’m writing to address an ongoing issue with the On-Discover call, specifically related to the request ID. I want to emphasize that we’ve taken care to ensure that the correct request ID is being used in the On-Discover call, which we obtained from the Discover call response. However, despite these efforts, we continue to encounter the following error:
API URL: https://dev.abdm.gov.in/gateway/v0.5/care-contexts/on-discover
Error Details:
{
“error”: {
“code”: 2500,
“message”: “No mapping found for resp.requestId on cache”
}
}
To provide a comprehensive view of the situation, I have attached a new screenshot of our workflow for your reference. This screenshot demonstrates that the request ID we’re using in the On-Discover call is indeed sourced from the Discover call response.
