The objects are getting stuck in “Resolving variables” state. This state isn’t allowing the jobs to kick start on their own despite the successful completion of their predecessor jobs. Hence, users have to manually start the successor jobs as soon as they get stuck in the status mentioned above. We noticed that objects with Variable reference were getting impacted with such error. Not sure how to troubleshoot this error. Could anybody help us resolve this issue?