Approval triggers same workflow twice

[Nithin21]

Came across a scenario where same Workflow is triggered twice when change request approval is done. This happens randomly and not able to reproduce even though i follow same sequence of events

When workflow is triggered the first time, history of change request captures tasks being generated as part of workflow
When the workflow is triggered the second time, history for change request does not capture change tasks being generated.

Seek inputs on how / where to analyse

Also , what would cause change history to not capture the task being generated second time

[Chuck Tomasi]

Without being able to reproduce this, it's going to be difficult to identify where the issue is. I would start with system logs, event logs, workflow context (and related list logs on that context). I also recommend working with customer support on this one. They may have access to resources you do not.

[Nithin21]

In the related list on workflow context, i could see a record stating that workflow is triggered for second time by Task Approver'

The workflow looks for Type = Major.

When approver clicked on Approve button i do not see a scenario for Type to change

Even if Type changes old Value = Major and newValue is also = Major.

As there is not difference between old Value and new Value, am thinking what would cause workflow to trigger

Also at the same instant there is a default SLA workflow that changes is created.

Would it be possible for this SLA workflow to re-trigger workflow on change ticket as approval is done at same instant

[Jace Benson]

It's hard to guess without more information. 

I'd guess though the conditon to start the workflow/run the business rule or whatever it is that triggers the task watches for a condition where a fields is a value, and you should change that to field.changesTo(value)