This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 95%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Any idea why this schedule resulted in execution today 9/1/2020 when September is not selected?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 76%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Had the same issue today as well with reports scheduled for Oct 1st.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 70%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERT%3C/text%3E%3C/svg%3E)
The SSRS creates a SQL Agent Job to execute the report. I'm guessing that you changed the subscription to the report at some point in the last month. What happens when you update a subscription is it drops the old Job and creates a new one. With the ones scheduled for Quarterly in SSRS it uses the SQL Agent's schedule logic which is to run every three months after the start date, but when the the job is recreated it loses the last run date for the Job that it uses to calculate the third month to run in, and so it just starts with the next month. There are ways around this, but I find it is easier to just delete the old subscription each time and create a brand new one, instead of editing the existing one and having this issue.
Thanks, but I'm confused why it would be treating it as 3 month interval. I'm not doing it on an interval basis I've selected specific months to run not all of which are three months apart, notice June is off cycle it is 4 months since February and 2 months until august.
Here is a good explanation of the concept, but using something other than SSRS. The logic of the SQL Agent Job schedule is different than how it displays in SSRS's Report Manager. So logically it is simpler to save run every three month from a date, than to make four Jobs to fire it only on those months. The problem is that updating the subscription causes the SQL Agent to lose data that is vital for the Job to fire correctly.
Hi,
From the screenshot it should not behave like this , I suggest you to find the corespondent SQL Agent job for this subscription, and check the schedule in the job, see if in the job, it has same configuration.
Another thought is that your case is much like this thread: SSRS Subscription Not Running On Correct Months
Have you made this subscription in the middle of August ? That may let SQL Server determine 1st Sept. is the nearest for 1st Aug. this year, that may cause this behavior.
Best Regards，
Joy
Is there any way to check this without having access to the agent? Is it in some table I can query? I'm unlikely to be granted direct access to the agent. Company policy and so on.
It is just a double check, see if anyone has change the schedules in Agent Jobs. (Normally it would not happen, just in case.) You could ask other admin to check it if necessary.
But I tend to believe the case in the above link is your case which is by design behavior for this special situation.
Hi @Smith, Stephen M ,
Has your issue been resolved?
If you have any question, please feel free to let me know.
Regards,
Joy
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 61%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFD%3C/text%3E%3C/svg%3E)
I just had the same problem with a report designed to run quarterly, Jan 1, Apr 1, etc, but which was triggered on Feb 1. SQL Agent job looks fine, and no changes were made recently, so don't understand how the report was sent out. This is SSRS 2016.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 43%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
This same thing happened to me. I had subscriptions set to run on the last day of the quarter for some and the first day of quarter for another and the ran on Jan 30 & 31 and Feb 1. The DBA found that the start date was set to a future date however I had not made any changes to these reports or subscriptions and they had ran as expected previously.
I suspect some update occurred