Datto RMM v15.2.0 - Pinotage (EU1) - Device Filter Issue

Final update

This incident is now resolved after the Kaseya R&D team restored prior device filter functionality with an update over the weekend If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them.

1. Resolved · Oct 26, 21:12 UTC
   This incident is now resolved after the Kaseya R&D team restored prior device filter functionality with an update over the weekend If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them.
2. Monitoring · Oct 26, 10:12 UTC
   An update was deployed to Pinotage (EU1) over the weekend to restore standard device filter evaluation behavior. Our internal testing confirms that filters are functioning as expected, and all automated tasks are running smoothly. We are actively monitoring platform performance across a full business day before marking this incident fully resolved. If you paused any scheduled jobs or policies as a precaution, it is now safe to resume them. We will post our next update at the end of the business day.
3. Identified · Oct 23, 19:52 UTC
   We are actively addressing an issue affecting device filters that utilize compound criteria, such as "does not contain" combined with nested logical operators. Engineering is preparing an update to restore previous filter evaluation behavior. The build is currently being validated in our staging environment, and we will provide an update once the production release window is confirmed. Recommended Actions: Filters: No action is needed on your existing device filters. Existing configurations will evaluate as expected once the update is deployed. Automations: As a precaution, partners may choose to temporarily pause or defer non-critical scheduled jobs or policies that target dynamic filters until the update is complete. We will post our next update once staging validation concludes.
4. Identified · Oct 23, 14:51 UTC
   We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria. A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated. We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.
5. Investigating · Oct 23, 14:50 UTC
   We are aware of a issue affecting device filters that combine negative query conditions, such as “does not contain,” with an embedded AND/OR operator within the filter criteria. A change with how these conditions are evaluated was made to correct these queries however it was not communicated as expected and may cause some existing filters to return different results than previously anticipated. We are considering reverting this change, if you believe your filters may be affected, please contact Support for assistance reviewing your configuration and guidance on next steps.