Writing a trigger to handle updating a few fields on a record (of the same object, this is an Account to an Account lookup) when it is attached via a lookup relationship (ie. it is the parent or looked up to record), the trigger is an aftertrigger actually but my question more concerns general trigger behavior.
My expectation was that the Child record would fire first considering that is the record actually being changed. I honestly wasn't sure if the parent record being attached would even fire an update trigger but checking the debug logs, that does not seem to be the case, it appears the BeforeUpdate trigger for the parent record is the one firing first, then a BeforeUpdate for the child, then AfterTrigger for parent, BeforeUpdate for child.
This Org is a bit messy with a significant amount of managed packages and a a lot of workflow rules so question is if this is standard behavior or i have something odd happening in my org. Spent a good amount of time googling but didnt find much on this question. If its standard behavior i can certainly design my trigger to assume the initial record coming in will be the parent record (again it is a lookup relationship being created between two objects of the same type)