Known Issues & Workarounds
Last updated: October 19, 2026
This article documents confirmed bugs, their current status, and any available workarounds. If you are experiencing an issue not listed here, please contact LDARtools Support.
Section 1: Issues With an Upcoming Fix
The following issues have a confirmed fix scheduled for an upcoming release: Friday, October 30, 2026.
Backdated Component Profile Changes Missing From MOC History and Reports
Product: Chateau, Components | Expected Fix: Friday, October 30, 2026
When a component's profile is changed (for example, to Deactivated or TU Purged) with an effective date that is earlier than the component's most recent edit, Chateau records the change on the day it was saved instead of the effective date you entered. When this happens, the change does not appear in the component's MOC History or on the Historical MOC Porch, and it can be left off date-based reports such as the Deactivated report for that period.
Workaround: When possible, enter profile changes on or close to the date they take effect. If you have backdated a profile change and it is not showing in MOC History or on a report, please contact LDARtools Support and we can help identify the affected components.
Section 2: Issues Currently Under Investigation
The following issues are currently known and being investigated. Expected fix dates will be updated as development progresses.
Component Grid Query Clears After a Multi-Edit Save
Product: Chateau, Grids | Expected Fix: To Be Determined
After saving a Multi-Edit from the Component Grid, both the grid results and the grid query are cleared. You have to rebuild the query to keep working with the same set of components.
Workaround: Before opening Multi-Edit, make a note of your query filters so you can quickly rebuild the query after saving.
OOOOa Report Can Include Extra Inspections and Export Incorrectly to Excel
Product: Chateau, Reports | Expected Fix: To Be Determined
The OOOOa Report (Reports > OGI > OOOOa Report) can include Method 21 inspection data along with OGI data, and an OGI retest performed on a later day can appear as its own survey row. When exported to Excel, some column headers can appear merged or blank and dates can display incorrectly. The report may also have trouble running when a very large number of LUnits are selected.
Workaround: Review the report's survey rows against your OGI inspection records before using it for regulatory reporting. For the most readable output, view or export the report as a PDF instead of Excel. If you are selecting a large number of LUnits, try running the report in smaller groups of LUnits.
Early Retest Does Not Satisfy a Retest Request Created Later in the Day
Product: Chateau, Schedule | Expected Fix: To Be Determined
Some Retest inspection requests are created by a scheduled process each morning. If a passing retest is recorded before that request is created, the leak closes correctly, but the Retest request stays open. The tag keeps its due date and remains in its tour.
Workaround: If a component with a closed leak still shows a Retest due or remains in a tour, please contact LDARtools Support so we can clear the open request.
Database Administrator Access Not Shown on a User's Assignments Tab
Product: Chateau, Majordomo | Expected Fix: To Be Determined
In Majordomo, a user's Assignments tab lists the databases they have roles on, but it does not list databases where they are a Database Administrator. Because of this, a user can be deactivated while still listed as an Administrator on one or more databases.
Workaround: Before deactivating a user, check the Administrators tab on each database they may have managed and remove them there. If you need help finding every database a user administers, please contact LDARtools Support.
Chateau Mobile Check-In Can Time Out When Several Technicians Check In at Once
Product: Chateau Mobile | Expected Fix: To Be Determined
When several technicians check in to the same database at about the same time, one check-in can fail with an "Execution Timeout Expired" message while the others are still processing.
Workaround: Your data stays on the device. Wait a few minutes for the other check-ins to finish, then check in again. If the check-in still fails, please contact LDARtools Support.
Long Rule Names Can Overlap the Regulation Column on the Rules Tab
Product: Chateau | Expected Fix: To Be Determined
On a tag's Rules tab, long rule names can extend past the Rule column and overlap the Regulation name in the next column. This depends on the rule names in the database, your browser zoom, and your screen resolution. It is a display issue only and does not affect the rules themselves.
Workaround: Widen your browser window or adjust your browser zoom to make the rule and regulation names readable.
This article is updated after each sprint release.
Not finding your issue? Submit a support ticket and our team will look into it.