"Quarterly" is a common reporting period and SQL Server doesn’t have an efficient way to set up quarterly running schedules, it is more geared towards monthly or more frequently. What happens is when the job is re-deployed (or a server is upgraded), the start point for a quarterly run becomes the next instance of that frequency in the following month. E.g. if the job is set to run on the 15th of the month (January, April, July, October) but the job is deployed on the 9th of March, the first day it will run is the 15th of March.
Is there a way without my developers having to add a step 1 to check if the months are correct?