Unable to commit newly created Scheduled Script Excution

[Paul_Baker]

I am developing a new feature for our ServiceNow application that involves creating a new Scheduled Script Execution within the scope of the application. When going to commit my work through Studio's Source Control the newly created script does not appear in the list of modified files. The only way I have found that I can include the file is by checking the Include changes not tracked via the Customer Update (sys_update_xml) Table, but this includes files that should not be committed.
Is there a way to indicate to ServiceNow Studio that this file needs to be tracked within the repo?

[Tony Chatfield1]

HJi, OOB I do not believe that scheduled jobs (I assume you meant table 'sysauto') are added to update sets, which is why there is no record found in 'sys_update_xml' and the normal process would be to export\import the scheduled job via xml.

Here are a few potential solutions, but personally I would stay with OOB and just use XML.

SN Pro Tips — Force-Include Any Record Into an Update Set

Manually Add a Record to an Update Set - ServiceNow Guru

Add to Update Set Utility Documentation and Custom... - ServiceNow Community