Visual Not Exported Due to Timeout - Subscriptions

[kberge]

I have multiple reports with subscriptions and they work just fine, until recently. All of our reports use a Data Model and that is working fine, the data only takes a few minutes to load in the report. When I set up a subscription for two separate pages in the same report, I get the PNG image just fine for one, but not the other. It just shows an X with the text "This visual was not exported due to a timeout." 

I cannot find anyone else who has solved this issue and there are not any settings that I can find that will extend the timeout in the datasource or subscription settings. 

[v-yetao1-msft]

Hi @kberge 

If you delete the wrong subscription and then create the subscription with same report page , can this PNG image dispaly normally ?

Best Regards,
Community Support Team _ Ailsa Tao

[kberge]

@v-yetao1-msft I will redo the subscription and see if it works. Do you think that the subscriptions are needing to be re-done/refreshed due to some changes deployed to the report, causing the current subscriptions to fail?

Thanks,

Ken

[kberge]

@v-yetao1-msft  Removing and adding the subscriptions back did not fix the issue, I am still getting one page to work and one not. I did notice that it says the image was generated at 1AM, which is about the time our model finishes it's nightly refresh, so the snapshot is not generated when the report runs? I have an attached a screenshot. 

[DoAnVy]

I have the same issue 

[Ailbhe]

Any news? 

There is another similar issue without answer ...

https://community.powerbi.com/t5/Issues/This-visual-was-not-exported-due-to-a-timeout/idc-p/2904365#...

[kberge]

I just got off a meeting with Microsoft Support and apparently this is a bug. It has been reported to them as a bug and the Microsoft Development team is currently working to fix it, but they do not have an ETA at this time. So we will have to watch for it in the Power BI updates. I will follow up if I hear from them reagrding a possible date the bug will be fixed. 

[Inácio]

Same issue, but on power automate export from power bi