All,
Has anyone else see the following happen? We had a Mass Update somehow trigger a Workflow that never had it's criteria met. Let me explain.
The Mass Update was a super simple one. It simply copy the status of a Customer record to a custom field. That's it.
When it ran, however, the a bunch of fields on the Customer record were modified. In fact, the field changes were EXACTLY that of a State1 in a Workflow who's criteria would have never fired against this record. I know this to be true as there are static values that only the Workflow enters into these fields.
Further, none of the records that were affected in this way meet the criteria to enter that Workflow.
Lastly, according to the Workflow History .. these records never appear to have entered this Workflow.
The evidence is clear that this workflow affected this records as the field changes match 1-1 with its first State actions.
This was reviewed by Netsuite Support and because they could not reproduce the problem, its case was closed. Despite pleas of getting the case escalated, it remains closed with the premise that if it happens again, we'll have a stronger case.
The issue is this took us 7 hours to 'restore' those values and cost the client a days worth of working those leads.
I cannot wait for this to 'happen again'. Is there anyone else that has experienced this?
Summary: Mass update ran to set a custom field not referenced anywhere else in the system. A workflow that has criteria on it that NONE of these records matched was fired. The Workflow History on the records does not show the workflow EVER being initiated. We know for a fact it was this workflow because several of the fields that were updated on the targets of the original mass update were 1) not part of the mass update 2) at the same time stamp in System notes as the update 3) exact string copies from the workflow that does not show as firing. This was on 4400 records.