Firestop Clash Management did not find any clashes

This article will go over troubleshooting steps for when FCM does not detect clash/firestop locations in your model

Firestop Clash Manager (FCM) relies on data in your model to find clash and intersection locations to locate areas where firestopping would be required and provide product/system recommendations. If you run FCM and are not detecting any clash or intersections there are steps you can take to determine if there is an issue with the model preventing FCM from functioning as intended.

1. Are you running FCM in the architectural model or a linked model? FCM was designed to be run within the architectural model but can be used on linked models. When working in a linked model it is important to copy and monitor any walls and/or floors that you are firestopping into your project (Link to Copy and Monitor within Revit 2022). This pulls data from the architectural model into your linked model, enabling FCM to detect these assemblies, find service clashes, and provide recommendations on systems and products.
2. Are your assemblies connecting? When detecting joint locations, FCM finds locations where assemblies clash/intersect one another in the model or are within close proximity to one another. If FCM is not finding a joint clash the assemblies may not be intersecting within the model and are too far apart for FCM to register them as an intended joint application.
3. Have you run FCM on this section of your model previously? When FCM finds clash locations it places markers in your project as placeholders. If you run FCM on this location of the model again it will only find new clash locations and not  detect previously found/addressed clashes.