A network error was encountered / error fetchind data for this visual

[faronicus]

I have a user (and it is always one user, seemingly random) who can't see one of my table visuals in my published report. 

The only way I can fix this is by rebuilding the visual, but lo and behold, I get an email a few days later saying that he got the same error message.

On the report, the visual is blanked out and says "A network error was encountered. Please check your connectiona dn try again."

On the "more details" window, it says "Error fetching data for this visual. Please try again later."

It is always just one visual...and I have 4 table visuals on there; the others work fine, and they are all connected to the same sources.

Is there a permanent fix to this issue besides me rebuilding the visual every day?

Thanks

[rohit1991]

Hi @faronicus ,

This issue sounds like a frustrating one, especially since it only affects a single user and a single visual repeatedly. Based on the behavior you've described. The problem is likely related to rendering issues or client-side caching, rather than the data model or source itself. Rebuilding the visual temporarily clears the problem, but since it returns for the same user, it's likely their browser cache, network instability, or session state is interfering with the visual's ability to load.

As a more permanent fix, you could try the following:

• Have the user clear their browser cache or test the report in a different browser or incognito/private mode.

• Ensure they are using a supported browser and latest version (Power BI works best in Edge or Chrome).

• Check for any browser extensions (like ad blockers or script blockers) that may be interfering with rendering.

• Consider adding that visual to a separate page or duplicating it with slight changes to force a different render path.

• If possible, test using the Power BI Desktop in View as Role or with their credentials to replicate.

If none of these help, you may want to open a ticket with Microsoft support, especially since the issue is so specific and persistent. It could be a backend caching bug or session-level corruption specific to that user.

[simonz99]

Could you fix the problem? I'm experiencing the same with one visual.

[Anonymous]

Hi @faronicus ,

Thanks for reaching out to our community.

Did lbendlin's reply help you? If so, please accept it.

If not, please check and ensure that the data source connection is stable and not experiencing intermittent issues. 

If you're using an on-premises data gateway, make sure it is properly configured and up-to-date.

Also verify that the user encountering the issue has the necessary permissions to access the data.

In addition, you can check the issue with the report by downloading it locally and refreshing it.

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

Are you sure this is not caused by an expired access token?

[faronicus]

No...what's that

[lbendlin]

Read about access tokens and refresh tokens.  Check your data sources for any access expiry mechanisms.