Known Issues & Workarounds - LDARtools
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: Sunday, September 6, 2026.
Emission Reports - Type and SubType Columns May Be Reversed
ChateauFix: Sunday, September 6, 2026
On some databases, the Type and SubType columns on emission reports can show swapped values, so a value that should appear as SubType can appear in the Type column instead.
Workaround
If you notice a component on an emissions report where Type and SubType appear reversed, please contact
LDARtools Support so we can confirm the correct classification and recalculate once the fix is available. Avoid relying on these two fields for reporting or citations until this is resolved.
Section 2
Issues Currently Under Investigation
The following issues have been confirmed and are actively being investigated.
Workarounds are provided where available.
Chateau Mobile - DOR Records Can Show the Wrong Work Order and Comments
Chateau MobileLeaksFix: To Be Determined
When opening an existing Delay of Repair (DOR) record in Chateau Mobile, the Work Order tied to that DOR may not display, and the Comments section may show the comment from the original leak record instead of a DOR specific comment. The date shown can also reflect the leak's opened date rather than a DOR specific date.
Workaround
If you need DOR specific details on a component in Chateau Mobile, log them as a comment on the leak record for now, and confirm Work Order numbers in Chateau on desktop until this is corrected.
Excess Inspections Porch Can Show a False Excess Valves Alert
ChateauPorchFix: To Be Determined
The Excess Inspections porch can generate a false Excess Valves Only per Hour alert even when a technician's actual inspection count is well under the configured pace threshold. Expanding the alert to view the underlying inspection records can also show no data.
Workaround
If an Excess Valves alert does not match the technician's actual inspection count for that day, you can disregard it. Contact
LDARtools Support if you need help confirming the correct count.
Condensed Data Leak History Report Can Include Leaks That Should Be Excluded
ChateauReportsFix: To Be Determined
The Condensed Data Leak History report does not currently apply the same filtering used by Full Data Leak History and Simplified Leak History. It can include leaks closed as Component Mis-Identified, and can include a component with a blank leak section when its only leak activity falls outside the selected date range.
Workaround
For the most accurate leak history within a specific date range, use the Full Data Leak History or Simplified Leak History report until this is corrected.
Reactivating a Component From TUx Can Trigger an Unexpected Initial Inspection
When a long standing component with inspection history is switched from a TUx profile (TU Purged or TU In Service) back to Active, it can be scheduled for an Initial inspection instead of resuming its normal recurring inspection frequency.
Workaround
If a reactivated component shows an unexpected Initial inspection, please contact
LDARtools Support so we can verify the correct schedule for that component.
Comments
0 comments
Please sign in to leave a comment.