Question:
In Control Hub Cloud/On-Premise, jobs fail to run after no configuration changes with a "REST API call error: java.lang.NullPointerException" (example below) in the logs.
Answer:
In SCH, if the original creator of the job is no longer part of your organization, Control Hub pulls null values from the database which causes jobs to fail on start. This is a bug found in Control Hub 3.12.0 and has been fixed in Control Hub 3.14.0.
For Cloud users, as a workaround, we can replace the deleted user with an active user by making changes to the database. Please contact customer support to make the relevant changes in the database.
For On-Prem users, as a workaround, please run the following query in your database to replace the old user with a new user:
UPDATE JOB set CREATOR_USER_ID = <new-user> where CREATOR_USER_ID = '<old-user>'
