I'm experiencing some issues lately in the parcel fabric with point to edge snapping in several parcel fabrics I have been working with lately. Seems to be a version 3.3 issue - I only mention this because it seems to occur a lot ever since I upgraded
What is occurring when I click on "Generate Links within Tolerance" is that it successfully generates the links that it needs to for point > point coincidence, but when it needs to align points to line edges, it fails to, yet creates anchor points instead, keeping those points askew from the edges they need to snap to. The result is failure for points, lines and polygons to align for coincidence.
I've included a brief demo video (attached) that encapsulates this experience. What's odd is that this glitch issue happens sometimes, where it fails to point 2 edge snap, but other times, it successfully aligns the points to the lines. Can't seem to pinpoint what we are doing incorrectly or what may be configured differently that could fix this matter.
What I'm describing is a huge lack of functionality that is dependent on the alignment tool to work - I figure if it's a 3.3 issue, it must be widespread enough that maybe its a known issue.

One thing I MUST report is that the align tool works without this glitchy behavior in a fresh map with the fabric added from catalog. The video I have attached where we see the glitch is from a pre-configured map that existed in a project file that was created before 3.3. Some of the fabric layers were grouped and further configured beyond the default layering and grouping that take place with
I would like to know if that, if it is somewhat an issue with how the layers are configured in the current map, what is triggering the issue that can be configured around the matter. I don't want to believe that there is no flexibility to adjust anything in the default layer configuration when adding fabrics, only to risk losing functionality in the behavior of the tools, because the alignment tool worked properly in 3.1 for point 2 edge snapping, it should continue to work in the same map. In other words, I should not have to add parcel fabric controllers to new maps with every new release of Pro, if the ability for a tool to run properly is contingent upon layers in the table of contents being in a certain state that is most 'default' as possible from ESRI's configurations