Who messed with my config file?

I hit this doozy of an error in CRM when deploying code to a production environment today. Specifically when i was publishing changes to a workflow.

“AN ERROR OCCURRED WHEN THE WORKFLOW WAS BEING CREATED. TRY TO SAVE THE WORKFLOW AGAIN”.

WTF? So apparently when you have made unsupported changes to the CRM config file, when subsequent rollups are applied they don’t update the config file,  As it detects that it has changed and does not apply the latest updates to prevent the unsupported changes from being overwritten.

I’m looking forward to finding out who the tool was thought it was a good idea to makes changes to the config file on the production environment and then not tell anyone. There’s a straight shooter with upper management written all over them.

Thank god for Pablo Peralta and this blog he wrote last month, describing the cause and the fix. He probably just saved someone's life.