No, that would not work. We are a global team and there are really no times "outside working hours" as MST and IST are two of our standard time zones. Also as the job takes close to 5 hours (it is a large database) it is best to do the job on a Saturday morning UTC because this is Friday night for one team and Saturday morning for the other.

If the job fires in the middle of the week it causes issues with the team.

So, I need the job to run consistently on a Saturday 2am UTC once a month.

Ben F was looking at this request. Would an option for you be the first of the month but at a UTC time that is ahead of your teams working hours? This would give you a consistent monthly run that would do what you need?

User Story:

As the DevOps Admin I would like to be able to schedule workflow trigger to fire on the last Friday of the Month because I need the job to only happen once a month on a specific day of the week.

Problem Statement:

The Engineering team would like to have the PRODUCTION Database cleaned and cloned into a STAGE environment for QA testing. Originally, they wanted this done on a weekly basis on a Friday so that the Remote Q/A team could come in on a Monday (Sunday night) and have a "Fresh" database to do regression testing with.

After a couple of weeks however, the engineering team found that this was too often and didn't leave the QA team with enough time to do some longer testing before the state was wiped out and reset. So, the Engineering team decided that once a month was a better solution.

However, they wanted it done once a month with the same Friday cadence; just skipping 3 or 4 weeks between. Setting the job to the Last Friday of the Month.

The DevOps Admin then went into CircleCI and found that once you specify that you want the Trigger for the job on a Monthly, rather than a Weekly basis, you were forced to pick a day of the month rather than a particular day of the week. Since the day of the month could fall on any day of the week (and in fact could actually not happen if you picked a day like the 31st and the month didn't have that day in it) it was found to be unusable.

Since it has been now confirmed that CircleCI doesn't allow this functionality, the poor DevOps Admin will now have to figure out a way around this and probably end up with 3 or 4 failed jobs a month with 1 successful as the DevOps Admin will have to implement some scripting code to get around this.