Troubleshooting Common Scheduling Issues
Reports not running on time? We'll walk you through missed schedules, timezone problems, and how to verify your automation is actually working.
Why Reports Miss Their Schedule
Your report didn't send at 9 AM like it should've. Now you're wondering what went wrong. The thing is, scheduling failures usually come from one of three places: timezone confusion, account permissions, or the system genuinely not running the job.
Most folks don't realize that their scheduled time is set to a different timezone than their local time. You pick 9 AM on Tuesday, but the system's running in UTC, which means your report fires off at 2 PM instead. That's the single biggest culprit we see.
Second issue? Account permissions. If your user account doesn't have rights to run reports or access the data, the scheduler will quietly fail. You won't get an error message — the job just won't execute. That's frustrating because you're checking your email and wondering if something's broken.
Step-by-Step Verification Process
Follow these checks to find where the breakdown is happening.
Check Your Timezone Setting
Go to your account settings and find the timezone dropdown. Write down what it says. Then compare it to your actual location. If you're in Montreal but the system says UTC, that's your problem right there. Change it to Eastern Time and save.
Verify Account Permissions
Check if your account has "Report Execution" or "Schedule Management" permissions. If you're an admin, you should see these enabled. If you're a regular user, ask your admin to grant these permissions. It's usually a quick checkbox.
Review the Schedule Details
Open the specific scheduled report and look at every field: the day of week, time, and recurrence pattern. We've seen reports set to run on Saturdays that people forgot about. Double-check that Tuesday 9 AM actually says Tuesday 9 AM.
Test with a Manual Run
Don't wait for the schedule to run. Hit the "Run Now" button on the report. If it works manually, the report itself is fine — the issue is the scheduler. If it fails here too, something's wrong with the report data or permissions.
Important Note
This guide provides educational information about scheduling automation and troubleshooting approaches. Every system has different configurations and permission structures. If you're working with sensitive financial reports, consult with your IT team or system administrator before making changes to scheduling settings. Your specific setup may have additional requirements or constraints.
Common Issues Beyond Timezones
Timezone fixes solve about 60% of scheduling problems. But there's more that can go wrong, and knowing what to look for saves you hours of frustration.
Email Delivery Failures
Your report runs on time, but it never arrives in anyone's inbox. Check the recipient email addresses — we've seen typos that go unnoticed for weeks. Also verify that your email server isn't flagging the automated messages as spam. Ask your email administrator to whitelist the sending address.
Partial Data in Reports
The report generates, but it's missing data or showing old numbers. This usually means the report ran before the data source finished updating. If you're pulling from a database that syncs at 8:30 AM, don't schedule the report for 8:15 AM. Give it 15-20 minutes of buffer time.
How to Know If It's Actually Working
Once you've made changes, you'll want proof that the fix stuck. Don't just assume everything's fine now — that's how issues creep back in.
Check the job history or execution log. Most systems keep a record of when each scheduled report ran and whether it succeeded or failed. Look back 2-3 weeks and count how many times it actually executed. If you scheduled something to run every Tuesday and you see it in the logs for the last three Tuesdays at the right time, you're good.
Set a reminder on your calendar for one week from now to verify the next scheduled run worked. Seriously — put it in your calendar. That one extra check catches issues before they become bigger problems.
Quick Recap
Timezone is Usually the Culprit
Verify your account timezone matches your location. This fixes most scheduling problems immediately.
Permissions Matter
Make sure your account has permission to execute and schedule reports. Ask your admin if you're not sure.
Test Before You Trust
Run the report manually first. If it works manually but not on schedule, you know the scheduler is the issue.
Check the Logs
Review execution history to confirm reports ran when they should have. Look back 2-3 weeks to spot patterns.