Log entries in the BOQ form

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Debug errors or track any critical transactions during the execution of the test suites, setting up the Cloud Runner or generating the tests by viewing the log entries in the BOQ form.

    You can now view important log entries in the BOQ form. When you go to the BOQ table, you will see the list of jobs. On entering one of the jobs, you will see some specific job log entries.

    The following are some of the examples for log entries in the BOQ form for test execution.
    • Successful test runImage showing successful test run
      Note:
      Select See generated tests related link to view the automated tests. The list of generated tests shows up and is not editable. You can also view the state and the reasons of failure of the tests on the list. The See generated tests related link is visible for all the log entries in the BOQ form examples. Generated Tests list.
    • Test run got cancelled by user via root trackerImage showing canceled test run
    • If BOQ and BOS can be reached on an instance, but login is redirected.Image showing login redirected case
      Note:
      This might happen when the ADCv2 load balancer of the instance is misconfigured and you have a customization that redirects traffic via a client side script.
      (the ADCv2 load balancer of the instance is misconfigured, the customer has a customization that redirects traffic via a client side script, etc…)
    • If you have deleted an API key before the job is sent to BOS/BOQImage showing API key deleted case
    • If the BOS is unable to login to an instance due to some client side script, API key being deleted after request has been sent to BOS/BOQ, etc.Image showing unable to login case