Subscriptions sending broken data

[patreporting]

Some of my subscriptions show an error for the actual report screenshot. When I open PowerBI the data displays properly. Other subscriptions work fine. Screenshot of the error below.

[Anonymous]

@patreporting,

Is the above issue intermittent? Do you get this issue if you subscribe dashboard with Pinned Tiles instead (not pinned live pages)?

Besides, what is your data source and do you use on-premises gateway? 

Regards,
Lydia

[msteinwachs]

I am having this same issue and it is occuring intermittently. Subscription emails will occasionally send with broken data and error messages, however the report itself works fine when viewed within the workspace or app.

[Anonymous]

@patreporting @msteinwachs,

A similar issue has been reported internally. And please check PG's response.

"Our service renders the report as if the customer is accessing it. What ever may happens for the customer will happen in our service. We lack the detection of those types of errors. And, this is what we are working on. ETA is 2 months ".

Regards,

Lydia

[patreporting]

It is intermittent

This is a report, not a dashboard or pinned item of any kind

Our data source is multiple custom sql (MSSQL) queries via an on-prem gateway

[Anonymous]

@patreporting，

I know. I would recommend you check if you  get same error when you subscribe dashboard with Pinned Tiles instead (not pinned live pages).

Regards,
Lydia

[answain]

Experiencing the same issue, seem to have it narrowed down. If the subscription triggers while a refresh is in progress it will show an error like OP indicated.

It has become a major issue for me as we moved on to premium and the number of reports we have refreshing within our org has caused extended refresh times, so it is difficult to time refresh/reports properly to get up to date information without hitting this situation.

A poster higher up indicates that it is mimicing what an end user sees, but this doesn't seem to be the case as users can access the reports just fine during a refresh but a subscription will have this failure.