July 10th 2026 Release Notes

Don't forget our early-access features: if you are interested in trying them, please reach out to LDARtools Support.

• Auto Tours - Automatically build tours on a recurrence schedule. (Beta). 

• Dashboard - Redesigned operations dashboard with new compliance and performance widgets. (Beta). 

Chateau Release Notes – Fixes & Improvements

Leaks

• Fixed Chronic Leaks 5000 PPM Audit alerting inconsistently. When two qualifying leaks on the same component started at the exact same time, Chateau could mix mismatched details between the two leaks — for example, the ID from one but the date from the other — when comparing them, which produced an inconsistent result and could make the same situation trigger an alert on one Daily Audit run and not the next.

• Fixed overdue leak-response counts on the Operations Dashboard. The "Overdue Leak Responses" card flagged a leak as overdue once its deadline passed, even when the required attempt or retest had already been completed on time. The count now only includes leaks that actually missed their deadline.

• Fixed a crash in scheduled Leak Alert emails. If a leak or inspection comment contained a vertical bar character ("|"), as in comments like "ID: 40945 | Leak 4," that comment could stop that report's leak-alert email from going out.

• New editable AVO Close Why picklist. The AVO Event close-reason list can now be customized under Settings → Picklists, matching how other close-reason lists already work. The system-required "Leak Opened" reason cannot be hidden or removed.

Inspections

• Fixed a crash opening a pre-filtered Inspections list. Opening the Inspections list from a dashboard link, a saved query, or a specific component could crash the screen before the list finished loading.

Porches

• Fixed property names on the Unapproved Edits on MOC porch audit. The Property column showed the property's raw underlying name (e.g. "Isolatable Source") instead of the friendly label used everywhere else (e.g. "Isolatable Source").

• Fixed missing detail rows on the Excess Inspections Audit. Expanding a flagged row to see which inspections caused the alert used a different time window than the one that actually triggered the flag, so the drill-down often found no matching inspections and showed a blank panel instead. Both now use the same time window, so the detail rows always match what triggered the alert.

• Fixed Expiring Tech Certification alerts not re-triggering after renewal. Once a technician's certification alert had been cleared, renewing that same certification and letting it approach expiration again would not generate a new alert.

• Fixed New Component porch approval failures. Approving a batch of new components could fail with a generic error if the batch was affected by data left over after an earlier component was removed outside Chateau's normal process — for example, during a support-assisted cleanup. This blocked approval of the entire batch, not just the affected component.

• Fixed New Component porch approving components with a mismatched Type and Sub-Type. A previous, already-fixed issue in Chateau Mobile let technicians select a Sub-Type that didn't actually belong to a component's Type (for example, a Valve Sub-Type on a Connector component) when adding it in the field. The porch didn't catch this mismatch the way editing a component's details does, so invalid combinations could be approved without any warning.

• Fixed a blank "Original Value" on the MOC Historical grid. When a property change was suggested in Chateau Mobile and approved in Chateau, the "before" value on the Historical grid could show blank instead of the prior value.

• Fixed the Zero Leaks with ≥75% Inspections Audit alerting on stale data. This audit is meant to flag a unit only when at least 75% of its components were actually inspected during the current monitoring period with no leaks found. It could instead count inspections from an earlier monitoring period, so a unit could get flagged even when no inspections had happened yet in the current period.

Components

• Fixed deactivated components staying on tours and schedules. Deactivating a component didn't always clear its pending inspection requests from tours immediately — components could remain on a technician's schedule for up to a day.

• Fixed clearing a Sub-Type or Sub-Sub-Type not saving. Removing a component's Sub-Type (or Sub-Sub-Type) in Component Details Edit appeared to work in the confirmation dialog, but the change was silently dropped and the original value remained after saving.

• Fixed the Profile Change Why picklist on the TUx Log's Activate Selected Components action. Activating components pulled reasons from the Reactivate Why list instead of the Active Why list.

Resources

• Fixed duplicate analyzer serial warning not appearing for deactivated analyzers. Adding an analyzer with a serial number already used by a deactivated analyzer didn't show the usual duplicate warning, and saving failed with a generic error instead.

Reports

• Fixed incorrect Activated/Deactivated counts on the Periodic Inspection Report. The report counts components as Activated or Deactivated by comparing their status at the start and end of the period. Some genuinely activated components were being missed — for example, a component added during the period on a Temporarily Unavailable (TUx) profile that was later made active, or a component whose recorded "date added" fell outside the reporting window because of a backdated or import-related date, even though its actual status history showed it was activated during the period. Activated and Deactivated counts are now derived directly from each component's status history instead of its recorded dates.

Rules

• Fixed the Create Regulation dialog overwriting an existing regulation. On the Create and Edit Rules screens, entering a regulation value that already existed — including one you'd previously deleted — didn't warn you: it silently overwrote the existing regulation's details (and restored it, if it had been deleted) instead of blocking the duplicate. Chateau now blocks duplicate regulation values there and automatically removes any commas typed into one, since a comma could cause problems in other parts of Chateau that list a component's regulations together, such as on certain reports.

• Fixed an error from rapidly clicking Run Rules. Clicking Run Rules multiple times in quick succession could start more than one rules run at the same time; the runs could collide and fail with an error instead of completing. The button now disables itself while a run is in progress, so repeated clicks are safely ignored.

• Fixed the Rules tab showing an outdated frequency after a MOC approval. Removing an exemption (for example, changing Insulation to None) and approving the change from the MOC porch with rules run could leave the Rules tab showing the old exempt status instead of the new frequency.

• Fixed the MMQ Phase not refreshing after a DTM change. Changing a component's DTM setting from Yes to No could leave the MMQ Phase blank on the single-tag screen and in the Component grid until a manual refresh was performed.

Majordomo

• Fixed an issue that could lock users out of every database. Switching between databases in quick succession could occasionally leave you unable to do anything in Chateau until you manually signed out and back in.

OGI

• New: editable OGI Sensitivity Checks. OGI Sensitivity Checks can now be corrected after they're recorded — for example, a mistyped camera serial, timestamp, or a transposed temperature/pressure reading — with every edit tracked in a full history of who changed what and when. Editing requires the new Edit Sensitivity Checks permission.

API

• New optional media fields on public API endpoints. The LeakSummaries, DelayOfRepairs, and OgiInspections endpoints can now optionally return leak and OGI image/video URLs. This is off by default and won't affect any existing integrations.

General

• General bug fixes and stability improvements.

Chateau Mobile

Leaks

• Fixed repair attempts silently not saving after Save and Recheck. Chateau Mobile's check-in process could mistake two different repair attempts entered on the same component and the same day for duplicates and drop one of them, even though both were real and distinct. Check-in no longer discards an attempt just because it shares a component and date with another one.

Sync

• Fixed check-out failing with a generic communication error. Checking out from a large facility could time out and return a generic "unexpected error" message due to a slow calculation behind the scenes; check-out is now substantially faster.

• Fixed new components saving with incomplete or stale Temporarily Unavailable (TUx) information. Creating a new component — including by copying an existing template — could put it on a TU profile without requiring TU Source and TU Date Available, so components could sync with this information blank or copied over from the template instead of the values that actually applied to the new component. Chateau Mobile now requires both fields before saving a component on a TU profile, matching the existing rule on Chateau Web.

General

• Fixed tour sort not being used when monitoring. Changing the in-screen sort order (Route Sequence or Tag Number) on a tour's component list re-sorted the screen, but tapping a tag to start monitoring, and using Next/Previous, still walked the tour in the old default order.

• General bug fixes and stability improvements.