CI/CD inconsistency for Power Bi Reports

Hi Shivek - Thank you for responding and assistance. Please find the below.

I'm using Fabric REST APIs (fab deploy) to achieve the deployments to UAT environment.
1. I verified that the deployed semantic model in bi-uat is connected to lakehouse in data-uat and there exists no warnings too
2. I did perform the following command to check if the report is bound to semantic model in bi-uat and yes it is connected to the right semantic model
fab api -A powerbi "groups/${{ vars.UAT_WORKSPACE_ID }}/reports" --show_headers
3. We use only a single YML file that has 2 jobs, job-1 will deploy semantic model, refreshes semantic model. Job-2 will deploy reports.
4.I'm using Managed Identity that has contributor access to both workspaces, data-uat and bi-uat.
Just to give you the current process approach. The CI (build) is, will upload the code as artifact. The CD (deploy) is, will download the artifact, replace the workspace id and lakehouse id of dev with UAT ids and deploy
I'm not able to identify which is causing this issue, but I believe there is something thatbis causing this issue.

Appreciate your help if there is anything I could check to fix this issue.