In this version, we add a new feature that lets you limit the number of retries when a report schedule fails and fix a few minor bugs.
January 5, 2022 - Available on the AppExchange
January 6, 2022 - Automatically pushed to all sandboxes
January 10, 2022 - Automatically pushed to all production orgs
Sometimes reports fail just because the Salesforce reporting API is taking a long time to respond. Since we're a native Salesforce app we can only wait two minutes per Salesforce's callout limits. In previous versions, Report Sender would send the user an error email with the "Read Timed Out" error and then try again in an hour. If it failed, Report Sender would keep trying each hour until the schedule was deactivated or the report was returned in less than two minutes. But now, we've changed that. When creating a schedule, you can set how many retries you want. We've set the default to "Retry Immediately" which we've found to have the most success for reports that barely go over the 2-minute timeout. But feel free to customize this to your needs.
Additionally, we've added to the list of errors that don't get any retries. For example, if we can't log in to the reporting API because an admin revoked access, we just send an error email and don't retry.
Fixed an issue where all report schedules were showing up on "My Report Schedules" tab.
Fixed a null error when editing a report schedule for someone else and you can't view their report (for example, when it's a report in someone's private folder).