Cogo traverse moves after hitting finish button

[CaitlinBernier1]

I am using ArcGIS Pro 3.5.2.  I have created a COGO traverse text file.  When I run it, it maps out the parcel correctly.  When I hit the finish button, it reshapes and move the parcel. I have attached 2 screen snips:

1. COGO imported from the text file.

2. parcel outline after hitting finish button.

I have experienced this before, a lot actually, but so far when using the Import ArcMap Traverse File, I had not encountered it.  Until today.  The existing pink parcel uses the same starting point.  Where I have experienced this before has been when using the same start point. Might be a clue or might be a red herring.

Anyone experienced this and have a solution?   Thank you for your time.

Caitlin

[Robert_LeClair]

So I wonder if the behavior you're seeing is related to BUG-000176312 - "When creating a polygon feature using the COGO Traverse tool, the Finish button in the tool's pane finishes the drawing differently than the Finish button on the Edit toolbar."  It was reproduced in ArcGIS Pro 3.4.3 and is in the Product Plan to be fixed.

It begets the question - which Finish button are you using to complete the Traverse?

[CaitlinBernier1]

I have tried both and have had mixed results.  Sometimes if I hit F2 to finish, it is OK; sometimes the Finish button works.  I know this is not helpful but I'll do some more testing when I go back to that project.  Thanks for your reply.

[CaitlinBernier1 · Accepted solution]

I got back into the project and did some very limited testing.  I found that if I right click and hit F2 to finish, the parcel stays in the right place, but if I use the Finish button on the Traverse tool, the parcel moves. It seems pretty consistent so it appears to be the same issue.  Thanks for letting me know about that bug.  I did search for something similar, I evidently did not use the keywords that described the bug.  

[Robert_LeClair]

Thank you testing your workflows.  It does seem to be related to BUG-000176312.  If you feel my response is correct, you may click the Accept as Solution button to close this thread.  Hopefully this BUG will be fixed in the near future.