Logging

The BQS Process Manager logs the process in the location specified in the batch configuration. The log is a .csv file with a name indicating the date the process was run and the name of the process, such as 20250122_AddrSync.csv.

The log entry for the start of the process indicates the user who started the process the name of the process, the current date and time, and the number of records to be processed. How the records are counted depends on the process.

  • For GIS to O&R processes the count is the number of GIS features.
  • For O&R to GIS processes the count is the number of Operations and Regulations records.
  • For Sync batches, the count shows both the number of GIS features and the number of Operations and Regulations records.

At the end of the process the BQS Manager adds a log entry indicating the date and time, the success or failure of the process, the duration, and the number of records analyzed and edited.

If you cancel the process, the number of records is 0. If you run QAQC in batches, canceling the process shows the number of records that have completed QAQC. For a Sync process, the number of records analyzed is calculated as follows:

  • If the process is run as a single batch and is not canceled, the count is the sum of GIS features and Operations and Regulations records.
  • If the process is run as a single batch and is canceled before QAQC, the count is 0.
  • If the process is run as a single batch and is canceled after QAQC, the count is the sum of GIS features and Operations and Regulations records.
  • If the process is run in multiple batches and is not canceled, the count is the total number of GIS features. (Because the Sync process doesn’t return Operations and Regulations orphans when run in batches, there is no way to determine how many records were actually checked.)
  • If the process is run as multiple batches and is canceled, the count is the number of GIS features that were sent to QAQC.

In addition to the BQS logging, there is a separate log function that may be enabled for the QAQC process in GeoAdministrator.

See QAQC logging.