Motion uses a different engine to render/export than viewing in the canvas?

I recently had a project where I did something in Motion where the camera pulled out to get a wider view of an object and then moved over to a new object. Plays fine every time in the canvas regardless of the settings. When I exported the file the camera pullback is ignored and it just moves straight to the next object without moving back first like it should. So this leads me to believe that Motion uses something else entirely when it exports and it does not use the same rules as the canvas even if you set everything to "same as canvas" when you export. The camera pullback is ALWAYS ignored. I was able to fix it by adding another behavior, but what happens in the canvas should always be exactly what happens when the project is exported. Otherwise the app is unreliable at best. You can't trust that what you're working on will export properly if two different sets of rules are followed. I've even seen it change fonts when exporting text. Is Motion just flaky?

EDIT: I have trashed my Motion prefs by holding COMMAND + OPTION while launching it. I'll update whether this worked or not.

EDIT 2 - It did not help. Apparently you can adjust keyframes on behaviors well after their play range has ended. The canvas obeys these keyframes, the exporting engine does not.

Without looking over your shoulder it's hard to know what to suggest but "ignoring the pullback" implies that you are not rendering the active camera. There is a dropdown menu i the 3D render section of the export settings.

My first thought was that I was somehow rendering a different camera. But no, they are both the active camera. It's kind of hard to explain, but the final rendered output is "correct" whereas what I was doing in the canvas was flawed. But honestly the canvas shouldn't let me do what I did. This was also confirmed by Mark Spencer who looked at my project.

The bottom line is to not add keyframes to behaviors after their out point. You can do that in the canvas and the canvas will obey those keyframes... which it shouldn't.