For certain databases, components where the monitoring Stream is not set to Default, the Component Grid shows the M21 Frequency and Last M21 Performed columns as blank, even though a monitoring frequency is assigned. Opening the individual component record shows the correct value.

When filtering the Closed Leaks grid by Close Why using Equals and selecting reason "Component Misidentified" from the dropdown, the search returns no results even though matching leaks exist. Using Like with a partial value returns the correct leaks.

Some dropdown picklists throughout Chateau take several seconds to populate with options after being clicked, causing a noticeable delay before you can make a selection.

On the Component Prompts page, an existing query built on the IsDor property still works, but it now displays as “Property removed,” and IsDor is no longer available to select when building a new query.

The Excess Inspections porch is generating alerts even when a technician's actual inspection count for that hour did not exceed the configured limit.

This porch audit can silently leave out past-due manual inspection requests for components that are missing certain grouping information, so some missed requests may not appear.

The OOOOa Report can fail to generate and return a connection timeout error, even when the date range and filters are reduced to a small amount of data.

When an inspection is added to a tour, the due date shown in the tour can be one day later than the actual due date on the component record.

Building a new tour from the Open Leaks grid can create two identical tours instead of one. Deleting one of the duplicates also deletes the other.

When a Tour Grid is exported to Excel, the column order in the exported file can no longer match the order shown in the grid, so columns you have rearranged come out of order in the spreadsheet. Component Grid exports are not affected.

Some users with Admin access and permission to add users do not see the Add Users button in the Users section of Majordomo, even though other users with the same permissions can see it.

Some users are unable to log in to Chateau Mobile by any method. Microsoft sign-in can go to a blank screen, QR code enrollment can return a service error, and password login can also fail.

After entering a value of 0 for the end-of-day drift check and tapping Save and Next, the screen can go blank and become unresponsive, requiring the app to be force-closed.

On the Component Quick View screen, a component with a long LUnit name can push the Type and SubType fields off the visible screen, making them unreadable.

The percent-inspected calculation on this porch audit can be inflated, showing a much higher completion rate than the actual number of inspections performed for the period.

The Agency Semi-Annual Report can fail to reflect recent component additions or count changes for some process units.

On the Full Data Leak History report, the repair attempts and readings table displays correctly in the in-database print preview but can shift to a second page when the report is exported to PDF.

The Post-Inspection Drift information for Cooling Tower inspections is not displaying correctly on the inspection record, and may show an incorrect time in Chateau Mobile.

If a technician adds an analyzer in Chateau Mobile using a serial number that matches an existing inactive analyzer in your database, syncing that check-in can fail with an error instead of completing.

The Date Opened timestamp on an AVO Event does not always match the time of the inspection that created it, though the date itself is correct.

EPA Method VVa (40 CFR Part 60, Appendix F) requires three consecutive drift readings per drift event, not a single reading. The current manual entry (and edit) captures only one reading per drift.