Skip to main content

I have a fellow System Admin who is able to create Report Subscriptions, but can't modify them, even subscriptions he created himself. He is just trying to modify the day and time that the reports are sent, but gets an error saying, "Subscription Unsuccessful. We couldn't set up your subscription. Try subscribing again. If you still can't subscribe, ask your Salesforce admin for help." He and I both have the same role and profile so I'm unclear why this is happening to him. 

 

#Salesforce Admin  #Reports & Dashboards

3 Antworten
  1. Heute 08:24

    Hi Erica, 

     

    Thanks for the extra detail — that rules out the limits angle completely, so let's dig further. 

     

    Since you both share the same profile but he's the one hitting this, the next thing to check is folder-level access — because in Salesforce, report/dashboard folder access is granted per user, role, or public group and is separate from profile permissions. Two users on the identical profile can still have different access to the same specific folder if it was shared individually rather than by profile. 

     

    What to check: 

     

    1. Open the report he's subscribed to, and check which folder it lives in. Then check Setup > that folder's sharing settings (or right-click the folder > Share in Lightning) to see his access level (Viewer/Editor/Manager) versus yours. If he only has Viewer access to that folder, that would explain why the initial subscribe worked (subscribing just needs run access) but editing/deleting the subscription fails, since Salesforce revalidates folder-level edit rights on save. 

     

    2. Check if the report was moved folders recently, or if folder sharing was changed after he originally subscribed. A report that moves into a more restricted folder after the subscription was created is a common way this breaks silently. 

     

    3. As a clean test: have him try to edit or delete a subscription on a completely different report that's sitting in a folder you know he has full access to (e.g., a public folder you both can edit). If that works fine, it confirms the issue is scoped to this one report's folder, not his user/profile in general. 

     

    4. If none of that turns up anything, this may be a stuck/orphaned CronTrigger record behind the scenes — at that point it's worth opening a case with Salesforce Support directly, since deleting an orphaned subscription record sometimes needs to be done on the backend. 

     

    Reference:

    https://help.salesforce.com/s/articleView?id=sf.analytics_folder_access.htm&language=en_US

     

     

    Let us know what you find on the folder access — that's the most likely lead given what you've ruled out.

0/9000