Forum Discussion

HaiVN's avatar
HaiVN
Helper III
6 months ago
Solved

Error

Hello,  I have several  Power Bi reports which published to service. I have published the reports to web ( using embed codes). Yesterday it was problem with som of the reports at web.  Some reports ...
Need Help
  • Olufemi7's avatar
    Olufemi7
    6 months ago

    Hello HaiVN, 

     

    The MissingJobResult error in Publish to Web usually means the backend query execution completed but the result could not be retrieved. This is commonly caused by:

    • Temporary Power BI Service/capacity issue
    • Dataset refresh running or recently failed
    • Heavy DAX/query timeout
    • Gateway or credential issue

    Please check:

    1. Does the report load correctly inside Power BI Service?
    2. Dataset → Refresh history (no failed/in-progress refresh).
    3. Data source credentials and gateway status.
    4. Try refreshing the dataset and generating a new Publish to Web embed code.

    In many cases this is a transient service issue and resolves after refresh/re-publish.

    Microsoft Docs::

    Publish to Web limitations 

     

    Refresh troubleshooting 

    If the issue continues, capture the Activity ID from the browser console and open a Microsoft support ticket.

  • HaiVN's avatar
    HaiVN
    5 months ago

    I fixed the error. Problem is one person  quited his job . He created the embed codes for the reports which had the problem. We changed the owner of embed codes and the reports works well! 
    Thank you all for helps!

v-sgandrathi's avatar
v-sgandrathi
Community Support
6 months ago

Hi HaiVN,

 

The MissingJobResult error in Publish to Web usually means the report query finished, but Power BI Service couldn't get the result. This can happen due to temporary service or capacity issues, dataset refresh conflicts, heavy DAX/query timeouts, or gateway/credential problems.

First, check if the report loads properly in Power BI Service. If it works there but not in the embedded view, it's likely a temporary or backend issue.

Consider these steps:

 

Check the Dataset -- Refresh history for ongoing or failed refreshes.

Verify data source credentials and gateway status if using on-premises sources.

See if the semantic model is Import or DirectQuery, since DirectQuery is more prone to timeouts.

Refresh the dataset and regenerate the Publish to Web embed code.

 

Often, the issue resolves after refreshing the dataset or republishing.