We have at least two workflows that changed trigger behavior yesterday. They have been in place for years without any changes to the triggers. Both are set to trigger upon record creation and field change. Starting yesterday, they have been running twice when the triggering field is populated upon creation. Previously, if a field was populated upon record creation, it didn't register as a field change for workflow trigger purposes.
For each instance where this is happening, one process session/job shows the start reason as "Record was created," while the other shows "Record field changed." Meanwhile, the audit history shows only a single event - create - that includes the value populated for the field. So I'm fairly certain there has been a change in workflow trigger behavior, where field change upon creation is now considered a field change for workflow trigger purposes.
I'm wondering if anyone else has noticed this, and if it is an intentional change by Microsoft that will remain in place. If so, I can remove the creation triggers on my workflows to avoid duplicate runs, but I'm reluctant to do so if the behavior may change again.
