Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
I'm using the personal gateway that attaches to my pc. Because I'm not on-premise sometimes it will not refresh(especially on weekends) and this is fine. I also get an email for these.
It seems that every week I find out that autorefresh has been disabled with no warning after a couple of days with refresh failures, which are expected and fine. When it's disabled I get NO emails that tell me it's been disabled.
I have to reset EVERY report's refresh schedule every couple weeks, and nobody knows that the reporting is down. This has big implications on my organization. How do I stop this from happening?
@Anonymous If you have shared this reports with others in the org, I would recommend using the normal gateway (Enterprise). Set it up on a Server, don't have any of these issues.
I realize this doesn't serve every purpose, but it is highly likely that the refresh is disabled because it is trying to hit an inaccessible gateway a number of times. Since it can't, it disables.
Another alternative would be to set up a personal gateway on a machine/VM that doesn't have downtime or can't be reached... However, that doesn't scale well as it is directly tied to your creds, but should work for what you describe.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 18 | |
| 7 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 51 | |
| 43 | |
| 27 | |
| 27 | |
| 25 |