Support > Forums > OpenBots Server > Job Status shows "Failed"

Job Status shows "Failed"

Rotfcoy

  • Reporter
  • Calender Icon February 04,2021 at 3:31 AM

Hi,

I have scheduled a published automation (ie. Open Firefox Browser) on OB Server but the Job status shows "Failed". When I viewed the Job on OB Server, the message is "Job is created through internal system logic." May I know what does that mean? Any other reasons why an Automation Job can fail?

This forum has 65 topics, 191 replies, and was last updated 9 months ago by Ghouse Shaik

Rodrigo Hurtado

  • Participant
  • Calender Icon April 03,2021 at 2:01 AM

Hi Nataly, i followed all posts about that issue and nothing works for me. Like others users, i have my OpenAgent connected to the server, credentials are domain\user and password well written and the status of the Agent is Healthy, but i can't make that the job runs. I have the same error and same error message of Roffcopy at his initial post, but the singularity is that the initial status of the job is "Assigned" not New, InProgress, Completed or even Failed, when the job crash, his status change to "Failed". i couldn't find information about the running tries in any log, not server either agent. By the way, my Agent has his logging sink type configuration as "FILE", but the file in the configured path doesn't have a line of log. My configuration is this:

  • Windows Server 2012 R2, VPN, with no domain
  • Sql Server 2012 express (already installed in the server, can't change it)
  • In the same server i installed the entire solution, Openbots Server, Agent and Studio.

I'll be greatfull for some help or orientation.

Best regards.

Nataly Alvarado...

  • Participant
  • Calender Icon February 22,2021 at 11:25 PM

Hello Rotfcoy,

From the description you provided, Manual scheduling is working as expected. The purpose of creating a manual schedule, is that you can deploy it at any time by manually clicking the "Run Now" button. I am also happy to hear that you are able to deploy processes dynamically through the Recurrence scheduling.

Please let me know if there is anything else I can help you with, enjoy your day!

Rotfcoy

  • Participant
  • Calender Icon February 21,2021 at 10:58 AM

Hi Nataly,

Thank you so so much once again. When i tried scheduling �Manual� and �One-time� automation according to UTC time, no job is created under �Job Status�. However, i am able to run it manually by clicking �Run Now� when i view it under �Schedule�. I am also able to run the job when i schedule it under �Recurring�. Therefore, I don�t think i see it as an issue now as i can just modify time period.

Nataly Alvarado...

  • Participant
  • Calender Icon February 19,2021 at 8:55 PM

Hello Rotfcoy,

Glad to hear you were able to run attended jobs. I would love to help you run unattended jobs as well. Please, tell me which type of scheduling you are having trouble with (manual, one time or recurring). Also, check if a job is created under the "All Jobs" server tab at the scheduled time. If so, check the "Job Status" of the job (New, InProgress, Completed, Failed). I would recommend to test the Manual scheduling first, to make sure server is communicating correctly with Agent. The execution should start inside a 5 minute window, and a job should be created. One caveat previously reported for One Time scheduling, pertains the difference in time zone between server and the machine running the process. Meaning, jobs are running at UTC time. This issue is currently being worked on.

Regarding a way to clear/delete jobs. This feature has been added for version 1.3.1, you will be able to delete individual jobs whose status is "New".

Rotfcoy

  • Participant
  • Calender Icon February 18,2021 at 5:16 PM

Hi nataly,

Yup i have built a completely new script and manage to run the published automation on the OB server as attended bot. However, nothing happens when i tried to Schedule the automation (make it unattended) There is also no error log message for automation Scheduling so i am unsure what is the cause. Btw is there any way to clear/delete the records under �Jobs�?

Nataly Alvarado...

  • Participant
  • Calender Icon February 16,2021 at 4:43 PM

Hello Gio and Rotfcoy,

I am glad to hear that Gio was able to run a job successfully. Please let me know if there is anything else I can help you with.

Rotfcoy, based on the log message you shared, the error is related to the commands included in the process you are attempting to run. One potential cause, would be attempting to run a process built on a previous version of OB Studio. The reason is that we have consolidated all of our commands and in result the older scripts (built in 1.2.) are not handled correctly by 1.3.0 Agent. In addition, commands nuget packages for 1.2. are not available on OpenBots Gallery.

Next release will include the ability to convert 1.2.* scripts to 1.3.0 through OB Studio. For now, please try to publish and run a process built in OB Studio 1.3.0 to confirm that this is the cause of the issue.

Best Regards,

Nataly

Rotfcoy

  • Participant
  • Calender Icon February 13,2021 at 9:35 AM

Hi Gio and Nataly

Many thanks for helping to resolve the issue. I followed Gio's suggestion to set the Username as the Domain/Username value from OB Agent's Machine Info but to no avail still.

Regarding to Nataly's queries, I have checked the Program under Control Panel, my OB Studio and OB Server both show version 1.3.0. However, when i go to http://localhost:81/auth/login to access to OB Server Login Page, the bottom text shows Version 1.0. As the OB Agent is installed together with OB Studio, I believe it should also be version 1.3.0.

The path to the Logs folder is C:\Users\Lenovo\AppData\Local\OpenBots Inc\OpenBots Agent and I could find the list of log messages. Based on the latest one, it shows "Log Message: Error occurred while executing the job; ErrorMessage = NuGet.Resolver.NuGetResolverInputException: Unable to find package 'OpenBots.Commands.Data'. Existing packages must be restored before performing an install or update."

What does this mean?

Gio

  • Participant
  • Calender Icon February 11,2021 at 10:35 PM

Hello Nataly and Rotfcoy,

Thank you for your help Nataly, I was able to fix my issue. My OB Agent showed that I had a successful connection by indicating the status as 'Connected', but I still could not get jobs to run on my machine. My issue was being caused by an incorrect Domain and Username value for the OS Logon Credential that I provided for my bot. I set the Username for the credential on OB Server as the Domain/Username value that OB Agent provides in the Machine Info setting, instead of splitting them accordingly. After I updated the credential with the correct Doman and Username I was able to run jobs successfully. Thank you for the help.

Nataly Alvarado...

  • Participant
  • Calender Icon February 11,2021 at 7:56 PM

Hi Roftcoy,

Currently, OB Server displays UTC as the default timezone. The upcoming server release will allow OB Sever to reflect the current machine�s timezone.

In regards to the failed job runs, I would like to ask you a couple of questions to better understand the root of the issue.

First, could you please provide the version of Agent and Server installed on your machine? Also, could you please verify the path to the Logs folder? To verify, check the Environment Variable Path provided for �OpenBots_Agent_Data_Path�.

Best Regards,

Nataly

Rotfcoy

  • Participant
  • Calender Icon February 10,2021 at 4:31 PM

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?

You are not authorized to reply, please click here to login and add your reply to this topic.