Leaks

New Last OGI Result, Last Inspection Date, and Last Inspection Type columns on the Open Leaks grid. 

Last OGI Result shows the pass/fail outcome of the most recent OGI inspection performed on that component since the leak opened; Last Inspection Date and Last Inspection Type show when the component was most recently inspected and by which method.

Reports

New per-database report title override. 

Support can now set a fixed title for a database that applies across every report — useful for databases that report under one company-wide name rather than an individual facility’s name.

Chateau Mobile

Components

New Comments tab on the mobile component detail screen. 

Technicians can now view and add free-text comments on a component directly from Chateau Mobile, with a badge showing how many exist. Comments recorded in Chateau appear on mobile, and comments added on mobile sync back to Chateau.

Tours

New component Type shown in the mobile tour component list. Each component row in a tour’s component list now shows its Type, so a technician can see a component’s classification without opening the detail screen.

Chateau

Leaks

Fixed OGI leaks reopening after a rule reassignment. 

A leak that had already been closed could reappear as a new open leak if a different OGI rule was later assigned to the component — even though nothing about the original leak itself changed.

Fixed exact-match querying on the All Leaks grid’s Close Why field. 

Querying “Equals” against a Close Why reason selected from the dropdown could return zero leaks — even ones genuinely closed with that reason — on databases where a Close Why’s saved value differed from its displayed label.

Fixed duplicate DOR closing records from a double-submit. 

Clicking Close on a Delay of Repair twice in quick succession could create two closing records for the same DOR, which could double-count DOR reads on compliance reports. A DOR can now only be closed once.

Cooling Tower

Fixed the Cooling Tower Inspections default query. 

Opening the Cooling Tower Inspections tab could show a broken query builder criterion, labeled “Date — Property removed” and grayed out, instead of the normal default date range. Separately, clicking “View N Inspections” on a Cooling Tower item in an Owner’s Porch Audit could take you to the wrong inspection tab entirely, or take you to the right tab but show every inspection instead of just the specific batch you clicked on.

Inspections

Fixed slow Location Unit selection on Inspection screens. 

After selecting a Location Unit on the Add/Edit Inspection or Cooling Tower Inspection screen, the Tag field could show blank for several seconds while it filtered the available Tags list down to that Location Unit, with nothing on screen to indicate anything was happening. A loading indicator is now shown while the Tags list updates.

Porches

Fixed missed inspections silently dropped from the Missed Inspections Scheduled by Request Audit.

If a component had no MMQ group assigned, no alert was ever created for its missed inspections — as if nothing had been missed, even when a manually requested inspection genuinely was.

Fixed false alerts on the Excess Inspections Audit. 

A component with a SubType and/or SubSubType assigned could have a single inspection counted up to three times — once each for its Type, SubType, and SubSubType — inflating a technician’s pace count and triggering false alerts.

Tours & Scheduling

Fixed Tour Excel exports not matching the grid’s column order. 

Exporting a Tour Grid to Excel could produce a different column order than shown on screen, and could include every column instead of only the ones the user chose to show — requiring manual reordering in Excel before printing.

Fixed tour due dates showing a day later than they should. 

Adding an inspection to a tour could show a due date one day past the component’s actual due date, because the tour showed the raw stored cutoff instead of converting it to the facility’s local due date.

Field Events

Fixed DOR Status missing from the Field Events query field list. 

The DOR Status field could no longer be selected when building a new query on Field Events > Component Prompts. An existing prompt already using DOR Status showed its condition grayed out and labeled “Property removed” — which looked broken — though the prompt itself continued to flag components correctly the entire time.

Resources

Fixed missing length validation on Location Unit names. 

A Location Unit name longer than 100 characters could be saved with no warning, and later cause any component assigned to it to fail saving with a generic error that gave no indication of the real cause. Location Unit names are now capped at 100 characters, with an on-screen message if the limit is exceeded.

Components

Fixed missing M21 frequency on the Component Grid. 

A newly added or imported component — or an existing component just placed on M21 monitoring — could show a blank M21 Frequency and Last M21 Performed date on the Component Grid right afterward, even though the correct frequency was assigned and visible on the individual component record. This happened because the process that updates those grid values ran a split second before the new monitoring assignment was actually recorded, so it found nothing yet and left them blank.

Reports

Fixed the OOOOa Report timing out on large databases. 

Running the report across many process units could fail with a connection timeout instead of completing.

Majordomo

Fixed database switching landing on the wrong screen. 

Selecting a different database from the database switcher could bounce back to the Overview screen instead of opening the chosen database directly, requiring you to select it a second time.

Fixed the Add User button not appearing for authorized admins. 

An Administrator granted permission to add users could still not see the Add User button in Majordomo, because a background token refresh didn’t pick up the permission change. Even logging all the way out and back in didn’t help, since that action often only silently renews the existing session rather than fully re-checking permissions.

General

General bug fixes and stability improvements.

Chateau Mobile

Sync

Fixed Chateau Mobile sign-in failing silently. 

Chateau Connection credentials could fail without showing any error, leaving a technician stuck with a blank screen and no indication of what went wrong. Sign-in failures are now shown clearly, and a failed automatic token refresh no longer blocks a technician’s next manual sign-in attempt.

Components

Fixed Type and SubType becoming unreadable on Component Quick View for long Location Unit names.

When a component’s Location Unit name was long, the Type and SubType fields could be squeezed into a single vertical column of one character per line. Both fields now keep a fixed, readable width regardless of name length.

Fixed a Check In failure from editing a component’s type in Add via Photo. 

Changing a component’s suggested type after adding it via photo could cause the app to also incorrectly reapply a leftover sub-type suggestion, creating a conflicting duplicate type record on that component. That conflict blocked the entire batch of newly added components from checking in.

Inspections

Fixed an M21 inspection Check In failure that could withhold an entire batch. 

If a technician started a new M21 monitoring inspection on a component right after finishing one on that same component — without navigating away first — the new inspection could inherit data from the one just completed instead of starting fresh. At minimum, it would be missing required timing information, which caused the entire batch of inspections recorded since the last successful Check In to fail. More seriously, it could also silently carry over the previous inspection’s peak PPM reading as its own, which could make it look like a leak was found when there wasn’t one, or hide a real one. Both problems are now prevented on the device.

Analyzers

Fixed the end-of-day drift screen freezing after save. 

Chateau Mobile’s check for whether a connected analyzer had a calibration on file that day defaulted to “yes” for TVA analyzers, regardless of whether one had actually been recorded. If a technician reached the end-of-day drift step on an analyzer with no same-day calibration, entering a reading and tapping Save and Next would freeze the screen completely, with no further input accepted and no way to recover except force-closing the app. The app now checks for a real same-day calibration — including on the drift step reached from a Cooling Tower Inspection — before allowing entry to the Input Drift screen, and shows a clear message if one hasn’t been done yet.