Roadmap
Follow the signal.
RefreshRadar is built in the open, and real usage sets the order. Here’s what’s live today, what we’re building next, and the ideas we’re weighing: three stations on one signal path. Step through them.
Live now
Everything below is live in the product today: real and working, not a mockup or a preview.
- Now live
Failure & silent-miss detection
Catches refreshes that hard-fail, get skipped, silently stop running, or get switched off, not just the ones that throw a red error.
- Now live
AI root cause, named with the fix
The moment a refresh fails, RefreshRadar names the likely cause and the fix: a verified catalog answer for common errors, or a live AI diagnosis for novel ones.
- Now live
Email & webhook alerts
The cause and fix land in your inbox, or in a signed webhook you can route to Slack, Teams, or anywhere else, the moment something breaks.
- Now live
Every workspace, every client tenant
One console watching every scheduled refresh across every workspace, and every client tenant you consult for.
- Now live
History past the 60-entry cap
A durable record of every refresh, far past Power BI’s native 60-entry limit. (Free keeps a rolling seven days.)
- Now live
Free error catalog & decoder
A no-login library of Power BI refresh errors: paste yours to get the plain-English cause, the fix steps, and the Microsoft source.
- Now live
A live demo, no login
See the real dashboard catching failures on sample data before you sign up or connect anything.
- Now live
In-app help & feature requests
Ask for help or request a feature right inside the app. Paid plans get priority support.
- Now live
Billing that forgives a blip
A failed card charge keeps your access and history through the retry window, and a missed payment webhook still activates your plan when you return from checkout.
Building next
Where our effort is pointed next. Committed direction, no fixed dates.
- Building
The rest of Fabric
Monitoring beyond today’s semantic-model refreshes: data pipelines, warehouses, Dataflows Gen2, and lakehouse / notebook jobs.
- Building
Recurring-failure fingerprints
Collapse every repeat of the same error into one standing diagnosis (“this hit 7× in 30 days”), with the shared cause and fix shown once.
- Building
Reliability scorecards
A screenshot-able health grade per dataset and per account: success rate, typical runtime, and trend over 30 / 60 / 90 days.
- Building
Refresh-health digest
A recurring reliability summary you can forward to leadership (incidents per week, share of clean refreshes), white-labeled on Team.
- Building
Chat alert cards for Slack & Teams
Alerts as a readable card (dataset, error, plain-language cause, fix link) posted natively into Slack or Teams, instead of raw JSON.
- Building
AI-drafted support replies
Faster answers in the help channel: AI drafts a reply grounded in the error catalog, and a human reviews it before it sends. Never auto-sent.
Exploring
Ideas we’re weighing, and genuinely open. Tell us which of these you’d want.
- Exploring
Root cause for “completed with warnings”
Diagnosis for partial successes, where a refresh technically finished but something quietly went wrong.
- Exploring
Slow / degrading-refresh alerts
A heads-up when refreshes start running long or drifting slower, before they tip over into failure.
- Exploring
Detection & resolution timing
How fast issues get caught and cleared, tracked over time, so you can see reliability improving.
- Exploring
Quiet hours & maintenance windows
Mute or schedule alerts around planned downtime, so a known outage doesn’t page you.
- Exploring
Public status page & freshness badge
A shareable, tokenized status page and an embeddable “data is fresh” badge for the dashboards you publish.
- Exploring
Team seats & shared boards
Roles and a shared console for a whole team, not just a single operator.
- Exploring
Ran-late / schedule-drift indicator
Flag refreshes that ran, but not when they were supposed to.
- Exploring
Durable-history feed
Pull your full refresh history into your own tools via a read-only API.
This roadmap is our current thinking, not a commitment or a delivery schedule. What ships next, and when, is shaped by what real users need, so the order changes. “Building next” is where our effort is pointed; “Exploring” is genuinely open.
Shape what’s next
The order here follows what you ask for.
Tell us what would make RefreshRadar a must-have for your Power BI work. The requests we hear most are what we build next.