Forum Discussion
Kudo CommanderSubscriptions suddenly failing with EmailSubscriptionCannotSubscribeOthersError
I'm looking at a subscription here for a user who has app access to a report in a premium workspace that's failing with EmailSubscriptionCannotSubscribeOthersError. I've (as admin) edited the subscription and resent it, whereupon it sends the same failure notification to the user. On the subscription in question, the user is listed as owner AND as the sole recipient.
EDIT: The only thing that's changed recently with this subscription is that I edited it yesterday to modify the End date.
This is a known Power BI subscription bug, especially common in Premium workspaces.
What the error really means:
EmailSubscriptionCannotSubscribeOthersError is misleading.
It can occur even when the user is the owner and the only recipient.Why it happens:
Editing an existing subscription (like changing the End Date) can corrupt the subscription metadata
Power BI then thinks the subscription is trying to send to “others”
Resending or editing as admin does not fix it
App access vs workspace access is not the root cause here
What actually fixes it:
Delete the subscription completely
Do not edit it further
Recreate the subscription from scratch
Ideally have the user create it themselves
Or recreate it as admin but ensure:
User has access to the app/report
User is owner and recipient
Wait a few minutes before testing
Backend cleanup is not instant
Things that do NOT fix it:
Resend
Editing recipients
Editing dates again
Admin takeover of the same subscription
3 Replies
- Amar_Kumar
Super User
This is a known Power BI subscription bug, especially common in Premium workspaces.
What the error really means:
EmailSubscriptionCannotSubscribeOthersError is misleading.
It can occur even when the user is the owner and the only recipient.Why it happens:
Editing an existing subscription (like changing the End Date) can corrupt the subscription metadata
Power BI then thinks the subscription is trying to send to “others”
Resending or editing as admin does not fix it
App access vs workspace access is not the root cause here
What actually fixes it:
Delete the subscription completely
Do not edit it further
Recreate the subscription from scratch
Ideally have the user create it themselves
Or recreate it as admin but ensure:
User has access to the app/report
User is owner and recipient
Wait a few minutes before testing
Backend cleanup is not instant
Things that do NOT fix it:
Resend
Editing recipients
Editing dates again
Admin takeover of the same subscription
MarkPalmbergThat's great. Thanks, Amar_Kumar . Do you know if there's an open issue for this anywhere?
- MarkPalmberg
This is still an issue.