Missing Entries In dbo.Jobs Table For The Jobs Id Entries In dbo.logs Table

News Knowledge Base
1

Why is there a mismatch in the "job IDs" within the "dbo.Logs" table vs the "dbo.Jobs" table in the Orchestrator database?


Issue Synopsis:
During an audit, there can be found instances where job IDs are present in the "dbo.logs" table, but the corresponding job IDs cannot be located in the "dbo.Jobs" table.


Root Cause and Diagnosis:

This issue could be experienced due to several possible reasons:

  1. One possibility is that an Attended job was initiated while disconnected from the Orchestrator. Disconnection can be caused by various factors, like network downtime or working remotely. In this scenario, the logs would be stored and retried on the robot machine (e.g., when the laptop reconnects to the network), but job creation and status wouldn't be updated automatically.

    To investigate this further, determine the exact time and machine the job was executed using the logs. After that, examine the event viewer on the machine during that timeframe for any Robot entries that could provide additional insights. If an Orchestrator or SQL crash occurred simultaneously, it could have caused this issue as job status API calls aren't retried, unlike the logs. The Robot application event log may hint at this, as it would register the failure to report the job status.

  2. If the network team confirms no connection issues, the problem could be due to triggering jobs in attended mode from the Studio. In this case, only the logs get stored in the database (since Development Logging is enabled by default), and job entries aren't created. This is an expected behavior of the system.

    Confirm this by checking the process names in the logs table for the missing jobs and comparing them with those that are present. Specifically, check if the environment name is tagged with the job name.

    For instance, if the "Baseproof Automation" process is run from the Studio while the Robot is connected with the Orchestrator, the process name in the logs table will appear as "Baseproof Automation". However, when run from the Orchestrator with the environment tagged, it would appear as "Baseproof Automation_EnvironmentName".