Memorable MemberSubscriptions set to send after a semantic model refresh are not delivered on the first attempt
Users report that email subscriptions configured to trigger after a semantic model refresh did not go out as expected on 2 and 3 October 2026.
What is reported in the community thread. The refresh itself completed, but the subscription emails were only delivered after 2 to 5 retry attempts.
Why this matters. There is no visible delivery status or retry log in the service, so owners cannot tell whether a subscription failed, is delayed, or was skipped.
Expected behavior. A subscription set to run after refresh is sent once the refresh completes, and any failure or retry is visible to the owner.
Source thread (reported by another community member, not independently reproduced) https://community.fabric.microsoft.com/discussions/power-bi-web-app/x/5372196
1 Comment
jubinsoniWhile delivery visibility is missing, a few options can reduce the impact. This is a suggestion list based on how subscriptions and flows are documented; I have not reproduced the reported delays.
- Add a buffer: set a time-based subscription a little after the usual refresh finish time, so a late or retried send still lands on time.
- Take control of the sequence with Power Automate: a flow that runs the refresh, waits for it to complete, then exports or emails the report, with its run history acting as the delivery log the service does not show.
- Add a heartbeat: have the flow or a scheduled check notify you if the expected email did not go out.
Refresh model (Power Automate: Refresh a dataset) -> Condition: refresh succeeded -> Export to file for Power BI reports / Send email -> On failure: notify owner (run history = delivery log)For the reported retries, the support ticket should include the subscription name, the refresh completion time and the actual send times, since those are what the product team can correlate.
So my overall approach would be:
Short term -> time-based subscription with a buffer after refresh Reliable -> Power Automate sequence with run history Escalate -> ticket with refresh time vs. send timesAI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.