Got it, thanks! I think I see why this is breaking. Currently you’re not allowed to use timestamp field in queries on rollup index. Because of this you can’t use rollup generated index in visualisation because dashboards is trying to execute range query on timestamp field.
This also why having rollup job with only timestamp field as dimension and no metrics would generate rollup index which would be unqueryable.
Note that it is: “enabled”: false. I enable it and it gets disabled again. Not sure how to troubleshoot that either.
This is expected since your rollup job is not continuous. It will disable itself after run is finished.