@Cognizant_Amit could it because of dpage cache data? Can you please run the dpage standalone with flushing dpage? If that's the issue please flush the dpage and then get the status. If you are using the dpage only once then that couldn't be the reason. But if you are hitting the dpage initially to get the initial status of child case, and then if the dpage is not flushed then that could be the reason.
@Anoop Krishna No, it's definitely not data page caching issue, we found another thread where PEGA acknowledged this issue as per that thread, however the recommended solution mentioned there (add post processing activity with some java steps) didn't worked out for our PEGA 8.8 version.