Forum Discussion
TOKEN EXPIRED
Hi jeanpcq
The error you're encountering—DM_GWPipeline_Gateway_MashupDataAccessError with a message indicating "Access token has expired, resubmit with a new access token"—is directly tied to your recent password reset. Even though you've updated your credentials in the data source settings and confirmed that your gateway connections show as "online," this issue suggests that Power BI Service is still using a cached or expired OAuth token for one or more specific data sources used by the two failing models. Power BI often caches tokens for efficiency, but when a user changes their password—especially for organizational accounts using OAuth (e.g., SharePoint, OneDrive, Dataverse, etc.)—the previously issued token becomes invalid and causes 403 errors on refresh, even if the gateway itself appears healthy.
What's particularly noteworthy in your case is that only two models are failing, while others that use the same table refresh successfully. This likely means that the broken models are holding on to outdated credential metadata that wasn't fully cleared or updated during your post-password-reset changes. Power BI Desktop refreshes work because Desktop reauthenticates using your current session, but Power BI Service relies on stored credentials or tokens.
To resolve this, go to the Power BI Service > Workspace > Dataset settings for each of the two failing models. Under Data source credentials, re-enter your credentials explicitly—even if it shows "Connected" or "Valid"—to force token regeneration. Make sure to do this for every listed data source in that dataset. After updating, manually trigger a refresh and confirm if it succeeds. If the issue persists, you may also need to open the report in Desktop, re-authenticate every source manually via Transform Data > Data Source Settings, save and republish to overwrite any lingering token references. This approach ensures that the Service uses fully refreshed credentials and not expired tokens tied to your old password.
Hi jeanpcq
The error you're encountering—DM_GWPipeline_Gateway_MashupDataAccessError with a message indicating "Access token has expired, resubmit with a new access token"—is directly tied to your recent password reset. Even though you've updated your credentials in the data source settings and confirmed that your gateway connections show as "online," this issue suggests that Power BI Service is still using a cached or expired OAuth token for one or more specific data sources used by the two failing models. Power BI often caches tokens for efficiency, but when a user changes their password—especially for organizational accounts using OAuth (e.g., SharePoint, OneDrive, Dataverse, etc.)—the previously issued token becomes invalid and causes 403 errors on refresh, even if the gateway itself appears healthy.
What's particularly noteworthy in your case is that only two models are failing, while others that use the same table refresh successfully. This likely means that the broken models are holding on to outdated credential metadata that wasn't fully cleared or updated during your post-password-reset changes. Power BI Desktop refreshes work because Desktop reauthenticates using your current session, but Power BI Service relies on stored credentials or tokens.
To resolve this, go to the Power BI Service > Workspace > Dataset settings for each of the two failing models. Under Data source credentials, re-enter your credentials explicitly—even if it shows "Connected" or "Valid"—to force token regeneration. Make sure to do this for every listed data source in that dataset. After updating, manually trigger a refresh and confirm if it succeeds. If the issue persists, you may also need to open the report in Desktop, re-authenticate every source manually via Transform Data > Data Source Settings, save and republish to overwrite any lingering token references. This approach ensures that the Service uses fully refreshed credentials and not expired tokens tied to your old password.