Hi Nataly,

Thanks for your response. My OB agent shows "Connected" and i have linked the active directory credentials to the agent with a valid date period. However, I couldn't find any Logs folder within my OB Agent folder in my laptop. Furthermore, the Automation Log tab on the OB server shows nothing while the Agent Detail shows "Available" and "Healthy" with Last Reported Message "Automation execution failed". I notice that the Last reported time does not match to my laptop time so is there a way to adjust the OB Server Time?

Hello Roftcoy and Giovanni,

There are a couple of factors that could be causing the jobs deployed through server to fail.

• Make sure the connection to agent is successful.
• Check if the active directory credentials linked to agent indicate a valid date.

If you are still facing issues after verifying the previously stated factors, please check the agent logs located at: ***MASKED_PATH***.

Please, feel free to share the obtained logs through this forum to help you troubleshoot.

Best regards,

Nataly

Hello,

I too am encountering the same problem. I published a project from OB Studio to OB Server using the Publish Project File Action, created a schedule on OB Server, then ran the job manually. The job status starts as 'New' then after a few minutes the job status changes to 'Failed'. This has happened with every attempt at running a job and with projects that are simple, like uploading a project that only consists of a Show Message command. The logs for each job are empty so I do not know what is causing the jobs to fail. The View tab for each job has the same message as Rotfcoy's "Job is created through internal system logic.". I have also made sure OB Agent shows a "Connected" Status before running the job. I'm not sure what could be causing this issue, any help would be appreciated. Thank you.