AnsweredAssumed Answered

Jobs/objects are getting stuck in "Resolving Variables" state.

Question asked by NARASIMHAGUDI607075 on Aug 2, 2018
Latest reply on Aug 3, 2018 by Antoine_Sauteron

Hello All,


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?