Sometimes when moving a production database to a test environment people may forget to disable various settings. For jobfile as of 3.7 there is now a safeguard if you should make this mistake which will cause jobfile to fail on a test system if this is done. This works by creating a hash of the connection string for the production environment which is put into jobfile and then compared to a hash generated at runtime. If these two don't match jobfile will ignore the request.

Find attached the executable required to generate the hash on the production system. This needs to be run in the same directory of the connectionstrings.config file. Once this is generated it will need to be added to the field sgApiSystemId in tblUsers on Jobfile

If there is a change in the connection string on production notify Jobfile immediately as jobfile will stop processing when there is a change in connection string