Why Aren't Scheduled Jobs Included in Update Sets?

[Rogers Cadenhe1]

I have a scoped app with a script include that needs to run once a day at 7 a.m.

To do this, I created a simple scheduled job that calls two functions of that script include.

ServiceNow doesn't include this scheduled job in the scoped app's update sets. There isn't a Force to Update Set UI action I can use to put it in an update set manually either.

Does anyone understand the rationale for why ServiceNow doesn't allow scheduled jobs in update sets? Because I can't do that I have to tell clients to create the same scheduled job three times: once in dev, test and prod. I'd prefer to avoid that.

[Prateek kumar]

You would have to import and export the scheduled job XML's to the different instances.

 Take a look at these options to force push records to update set

https://snprotips.com/blog/2016/9/7/force-include-any-record-into-an-update-set-in-servicenow

https://www.servicenowguru.com/system-definition/manual-update-set-inclusion/

[Trupti6]

Hi,

Scheduled jobs are not get captured in Update set directly, but you can export them as an XML and import them to your production environment that way.

[Rogers Cadenhe1]

Thanks for the tip. I wonder what would happen if I moved that single-record update into another update set's XML.

When I used git to publish and install a Studio app, it did include a scheduled job in the update. But git deletes and reinstalls the app every time it is used, wiping out all user data, so it can't be used for revisions to an application that's in current use.

[pawan k singh]

You can add Scheduled job in update set by clicking on Related links "Add to Update Set" option. It will move the xml to your current update set.

Please Mark this answer helpful/ if it helped you.

Regards

Pawan K Singh