Semantic model is failing to refresh

[kirah2128]

Dear All,

I have tried to reupload, and change the gateway connections and still I'm having the same issue. Is there anyone can understand how to resolve this below error? 

Data source error: {"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":

{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-04-21T07:05:13.2643413Z and was inactive for 90.00:00:00. Trace ID: 78219af4-0062-4351-963d-c173e3d41900 Correlation ID: 8da927a1-a606-404c-a7f0-7898a693dc45 Timestamp: 2025-07-30 06:57:12Z"}}],"exceptionCulprit":1}}} Table: amos_consumed_parts.
Cluster URI: WABI-NORTH-EUROPE-F-PRIMARY-redirect.analysis.windows.net
Activity ID: f2d909a5-d8e8-9c69-a46b-5d09b076b0c3
Request ID: 41e409e3-741d-5249-6c66-43c90ba81c3f
Time: 2025-07-30 06:57:13Z

Regards,

King

[v-kpoloju-msft]

Hi @kirah2128,

Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to @rohit1991, @jaineshp, for those inputs on this thread. Here I provided some steps those might be resolve the issue which is you faced. Please go through the below steps:

The error message you are encountering:  DMTS_OAuthTokenRefreshFailedError / AADSTS700082: The refresh token has expired due to inactivity

means that the credentials (OAuth token) used to connect your data source have expired because they haven’t been used in the last 90 days. This is a common issue when datasets aren’t refreshed regularly, or credentials haven’t been re-authenticated in the Power BI Service.

Re-authenticate the data source from Power BI Service: Go to the Power BI workspace where your semantic model lives. Click the ellipsis (…) next to your dataset Settings. Under Data source credentials, look for any prompts about expired or invalid credentials. Click Edit credentials, select OAuth2 as the method, choose Organizational account, and sign in. Click Apply.

Please manually trigger a refresh after credentials are updated to verify it now works. Set up a regular scheduled refresh (even if you do not need it daily). This helps avoid token expiry in the future. You can do this under the same dataset settings > Scheduled refresh.

Note: OAuth tokens expire after 90 days of inactivity, so having a refresh at least once every couple of weeks will keep the token alive.

Also, kindly refer to the below mentioned link for better understanding:
Solved: Semantic Model not Refreshing online, only in Desk... - Microsoft Fabric Community

Please refer to the below document link for more information:
Refresh a semantic model created from an Excel workbook - cloud - Power BI | Microsoft Learn

Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @kirah2128,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[kirah2128]

Ty so much for the help. The problem is solved.

[rohit1991]

Hi @kirah2128 ,

This error is pretty common when the data source token expires or the model is pointing to something that’s been moved or deleted. Here’s what’s worked for me (and my clients):

1. Go to your dataset’s settings in Power BI Service and re-authenticate the data source. Just updating the credentials often fixes token expiry issues instantly.

2. Double-check the target workspace, server, or database still exists and you have access. If anything was renamed, migrated, or removed recently, you may need to rebuild the connection not just update the credentials.

3. If the error keeps coming back, try fully removing and re-adding the data source connection (sometimes the internal pointer needs a “reset”).

4. If you’re using a gateway, make sure it’s up to date and pointing to the right place.

Pro tip: Set up a scheduled refresh, even once a month, to keep tokens active and avoid surprises.

[rohit1991]

Hi @kirah2128 ,

This error is pretty common when the data source token expires or the model is pointing to something that’s been moved or deleted. Here’s what’s worked for me (and my clients):

1. Go to your dataset’s settings in Power BI Service and re-authenticate the data source. Just updating the credentials often fixes token expiry issues instantly.

2. Double-check the target workspace, server, or database still exists and you have access. If anything was renamed, migrated, or removed recently, you may need to rebuild the connection not just update the credentials.

3. If the error keeps coming back, try fully removing and re-adding the data source connection (sometimes the internal pointer needs a “reset”).

4. If you’re using a gateway, make sure it’s up to date and pointing to the right place.

Pro tip: Set up a scheduled refresh, even once a month, to keep tokens active and avoid surprises.

[kirah2128]

Now, I got different error message

Data source error: {"error":{"code":"NotFound","pbi.error":{"code":"NotFound","parameters":{"ErrorMessage":"Server '265C00DA-F3AB-4254-81D6-AD7152744FBB' is not found."},"details":[{"code":"RootActivityId","detail":{"type":1,"value":"d9f3aa1d-9b49-458e-a003-71d1c02733d2"}},{"code":"Param1","detail":{"type":1,"value":"265C00DA-F3AB-4254-81D6-AD7152744FBB"}}],"exceptionCulprit":1}}} Table: amos_jobcard_fuel_tank_recording_A321.
Cluster URI: WABI-NORTH-EUROPE-F-PRIMARY-redirect.analysis.windows.net
Activity ID: 6ae9b868-ccec-c3dc-2fa5-1788b68f3a87
Request ID: e888cd73-b225-8eeb-4aac-e4d4f204065e
Time: 2025-07-30 08:21:11Z

[jaineshp]

Hey @kirah2128 ,

Looking at this new error, the issue has shifted from authentication to a server/resource not found error. The GUID 265C00DA-F3AB-4254-81D6-AD7152744FBB represents a server or workspace that Power BI can't locate.

Here's what likely happened:

• The refresh token expiry forced a re-authentication
• During re-auth, the connection may have referenced an old/deleted workspace, server instance, or cluster
• The table amos_jobcard_fuel_tank_recording_A321 exists but the server reference is stale

Resolution Steps:

1. Check Workspace Access
   • Verify the workspace containing your dataset still exists and you have access
   • Confirm you're connecting to the correct workspace/environment
2. Recreate the Data Source Connection
   • Delete the existing data source completely from your dataset
   • Add it back fresh with current server/database references
   • Don't just update credentials - rebuild the entire connection
3. Verify Server Details
   • If this connects to Azure Analysis Services or SQL Server, confirm the server name hasn't changed
   • Check if there was any recent migration or server consolidation in your organization
4. Gateway Configuration (if applicable)
   • Remove and re-add the data source in your gateway
   • Ensure gateway is pointing to correct server instances
5. Contact Your Admin
   • This GUID error often indicates infrastructure changes
   • Your Power BI admin may need to verify server migrations or workspace configurations

The "NotFound" error with that specific GUID suggests the authentication worked, but now it can't find the target server. Try recreating the connection entirely rather than just updating credentials.

Does your organization's IT team manage the data infrastructure? They might have insights about recent server changes.

Best Regards,
Jainesh Poojara | Power BI Developer

[jaineshp · Accepted solution]

Hi @kirah2128 ,

Your refresh token expired after 90 days of inactivity (issued April 21, expired July 30).

Quick Fixes:

• Re-authenticate the data source - Go to your dataset settings and update credentials with fresh login
• Check service principal expiration - If using app registration, verify the client secret hasn't expired
• Clear cached credentials - In Power BI Service, remove and re-add the data source connection
• Update gateway connection - Since you mentioned trying this, make sure you're using the latest gateway version
• For prevention - Set up automated refresh schedules to keep tokens active, or use service principals with longer-lived secrets

The error is pretty standard OAuth timeout - just need fresh authentication. Should be resolved within 5-10 minutes once you update the credentials.

Let me know if the re-auth doesn't work!

Best Regards,
Jainesh Poojara | Power BI Developer