@SyedQayamHussainA16740370 if the issue is that the data page is not bringing back the new results, then the first thing I would direct you to would be to make sure that the data page is flushed and is not using cached results.  After that, I would look into the workgroups themselves - does your application have access to them?  Is there some filtering condition that would make those results not appear?  If you are displaying these results on the UI - does the user have security access to view the instances (you mentioned that tracer showed no errors, so this one is probably not it)?  There are more things to check but these would be the first ones to look at.  

If all of these fail, then a sample of your configuration would be very helpful in trying to diagnose.

@SyedQayamHussainA16740370

This usually comes down to scope, context, or where the work groups were saved. First, make sure the new Work Groups are real data instances (Data-Admin-WorkGroup) in an unlocked production ruleset/version that’s in your application stack—not in a branch or a ruleset not loaded by your Access Group. Add at least one Work Queue to each Work Group and save; many OOTB lists filter out empty ones. Check whether D_CaseWorkGroups has parameters or filters (like org/div/unit, application, “available” flag) and that your new records match those values. In the tracer, “pxResults empty” often means a cached data page—open D_CaseWorkGroups and click Actions > Refresh, or flush it with pxForceRefresh; then log out and back in to reset operator/application context. Verify your operator’s Access Group actually points to the app where you created the Work Groups, and that your role has read access on Data-Admin-WorkGroup. If you’re on a multi-tenant or multi-org setup, confirm the org path of the Work Group matches what the report definition behind the data page expects. Finally, revalidate-and-save the application and clear rule/data caches if the list still doesn’t refresh.