Skip to content

QoS Conflict Rules

Every rule below is one QoS setting combination that breaks or silently degrades ROS 2 communication, and QoS Guard checks your publishers and subscribers against all 40 of them. Search or filter to find the ones that match your setup, then open a rule to see a concrete example, how to fix it, and the evidence behind it.

Each rule leads to one of three outcomes.

Won't connect the publisher and subscriber never match. Breaks a guarantee they connect, but a QoS promise silently fails. Wastes resources they keep working, but memory, CPU, or timing degrades.