Last week we released a slew of updates around the handling of Invalid Datasets. I know what you’re thinking…what the heck is an invalid dataset? Not to worry, I’ll explain. An invalid dataset is a dataset that simply failed to save successfully. As you can imagine, this doesn’t happen often. But when it does, it wreaks havoc in our app up, that is until last week.
Datasets may fail to save due to a variety of issues such as queries timing out, a disconnect with your datasource during the save process, etc. Out of over 20,000 datasets out there in BrightGauge land, only about 200 are invalid at any one point in time. The work we did was around how the gauge displays in the app when the dataset that powers it is invalid. If you see this on your dashboard or on a report it means you have a broken/invalid dataset. :
When this happens, your best bet is to visit the dataset page which will highlight in red which dataset is broken. If it’s a SQL dataset that you created, try a “Test Query” and see if the error presents itself again. If not, likely the dataset is timing out when trying to save to your datasource and typically that’s due to a data-overload! Slimming down the query helps this out or just contact us at support for more help.
Many times a quick “re-save” will do the trick as well. If you forget to try the resave, know that we will try the re-save at midnight your local time with the hope the dataset successfully saves at that time.
Once your dataset resaves the world rejoices and your gauges populate again with beautiful data and syncs commence. Maybe not the world rejoices but you will and so will we in the background.
This feature may not make the hair on the back of your neck stand up but it may save you one day from pulling your hair out when seeing the green spinner go on and on and on and on (that’s what was happening previously).