There are four reasons the Report Scheduler will stop running:

  • Your license has been suspended for failed payment (4 failed payments will force an auto suspend)
    • Confirm this by going to your list of "Installed Packages", Go to Setup > Installed Packages 
    • Find the Report Scheduler App
    • Confirm the "Status" value
    • If Status = Suspended, you can fix this by logging in at > go to My Account > find our App > Modify Credit Card Info
    • Within 5 minutes of updating this info your license will become Active again. Once you are active all functionality will automatically return
    • Call us at (480) 696-3812 if you need help with this

  • Your "Master Credentials" have changed.
    • Go to the "Scheduler Settings" tab:
    • Is this your "Username, Password and Token fields?
    • If this user has had any changes to either of these fields, he/she must update those changes on this page. Whoever these credentials belong to, this person MUST have the out of the box System Administrator" Profile.
    • The Report Scheduler will immediately return to being fully functional after completing this step.

  • Your "In Context User" is no longer Active
    • The Report Scheduler is running 4 different batch processes. Just like every other record in Salesforce, your batch process have an owner ... but for batches this is considered the "In Context"  or the "Submitted By" user
    • If your "Submitted By" user is no longer a System Administrator, or if this user is no longer an Active SF Licensed user, the Report Scheduler will immediately fail.
    • Go to Setup > Monitoring > Scheduled Jobs > then find each of these batch names: DashBoardSchedulerHourly, RefreshSchedulerHourly, ReportScheduleAnalyticsrHourly and ReportSchedulerHourly
    • Look at the name in the "Submitted By" column
    • If this user is NOT a System Administrator and or this user is no longer active, please have an "Active", System Administrator "DELETE" i.e.  click on the "Del" link before each of these names
    • After completing the "Deletes", immediately go to the "Scheduler Settings" tab and click on Save'
    • Once they click on the "Save" button these batch processes will immediately get recreated, inserting this users name to the Submitted By column
    • All functionality will return immediately after clicking on Save

  • Your organizations has moved to a custom login url
    • Go to the "Scheduler Settings" tab.
    • Navigate to the Master Credentials to Refresh Reports section.
    • You must update the following two fields in order to reflect your custom login url: 
      • Custom Domain Enable: (set this value to true)
      • Custom Domain. (no need to add the https, just enter using this format. 
    • The Report Scheduler will immediately return to being fully functional immediately after completing this step

  ---------------------- Other Troubleshooting items to check when only specific reports are not sending properly ----------------------

Your report may be too large:

Please keep in mind, that because the Report Scheduler sends our Reports via email, we are subject to Salesforce standard email attachment size limitations. Governed by Salesforce, Email attachment size is limited to 3mb, from the following link,

    The easiest way to determine whether or not you have a size limit issue is to go directly to the Salesforce Report and launch the report then export it.  Check the size of that file.
    1. If it takes too long to launch your report
    2. If you get a timeout error
    3. If the saved file is larger than 3 MB’s
    This report will not attach to the Report Scheduler. You should consider using report filters to reduce the size of your report. i.e. Modify the “Timeframe” from All Time, to Today, or This Week, or This Month, etc.

    If your credentials used on this page are not yours, you can test that they are correct by doing the following:
      1. Go to the User Settings “Login” Related list and look to see if there are any failed attempts by the Report Scheduler. You can also test your Credentials by doing the following:
        1. Go to the Settings Page
        2. Append the URL by adding the following to the end of the UR: ?debug=1
        3. Click “Enter”
      2. You will notice a 5th bullet point has been added, follow the instructions there to test whether or not your credentials are correct. If your page response is “True”, the credentials are correct. If the page response is “False” the credentials are incorrect. You need to make sure that the password and token are correct. NOTE: Do NOT append your password to the security token on this page. Only enter the full security token to the Security Token field.
    1. Make sure each individual Report and Dashboard that is being used in Scheduled Reports and or Scheduled Dashboards is not being stored in a private “My Folder”. If the “Current Context” User does not have access to the folder where any given report or dashboard resides, the report or dashboard will not get sent.
    2. Has your organization recently made any changes to the user login page? i.e. Have you moved to a "Custom Domain" for user login? If so, please modify the Master Credentials, adding your custom domain settings.
    3. Go to the Scheduled Report, then navigate to the following related lists:
      1. Refresh Log - are the logs indicating Failed? Or Success?
      2.  If you are seeing “Failed”, please go to #3 above and follow steps.
      3. Notes & Attachments - What is the "Last Modified" Time/Date?
      4. The last modified date/time here should coincide with the Refresh Log's last refresh date
      5. Email Log - Does this log coincide with the Scheduled Report timeline? i.e. If your Report was scheduled to send at 11 AM, are you seeing logs at or very close to 11 AM?
      6. If there are no, or missing Email Logs,
    4. You need to investigate whether or not the person who scheduled the Report has access to the data they’re scheduling.
    5. Double check the size of the files (report size) .. if you are trying to send thousands of records in a single file, there could be a size limit issue.