Sister-vehicle software pattern: campaigns issued for the R1T frequently apply to the R1S due to shared software stack. Cross-referencing R1T campaigns at any R1S service visit can be operationally relevant.
OTA campaigns that fail to apply are sometimes characterized as 'no action required' on the dealer side because no fault is actively stored. The failed application itself is the operative event and should be documented through the OTA history rather than only through stored faults.
Multi-campaign situations are particularly susceptible to incomplete documentation. A general 'software updated' note without enumerated campaign references creates ambiguity about which specific campaigns are closed.
Rivian app message threads can be modified or replaced when a ticket is updated. Local screenshots are the only reliable preservation of original message content for direct-service vehicles.