- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2019 01:43 AM
In workflow, there is a "wait for condition" activity which receives the two in arrows. After that all activities are triggering twice, and there is a "create event" activity in between which triggers notification. the notification has to be sent only once to the user which is going twice instead. i have verified the business rules to see if it is triggering the event which intern triggers additional notification, but there is no business rules which triggers the event.please help me on this.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2019 01:59 AM
Hi,
this actually seems logical to me. You have created two paths that both lead up to the 'Wait for condition' and then to 'Create Event', and therefor both paths do trigger the event. The 'Wait for condition' itself does not check if it has already been triggered by another path, it will just fire.
To avoid this kind of behavior, either remove the path between 'Run Script' and 'Wait for condition'. Another thought would be to just have the first three steps in serial (i.e. why are you branching between 'Run Script' and 'Wait for condition'?).
Or, add a variable to your workflow that is set to 'True' by 'Create Event', and have 'Create Event' check if the variable is 'False' before actually firing the event.
Kind regards
Ralf Schnell, Senior Platform Evangelist

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2019 01:59 AM
Hi,
this actually seems logical to me. You have created two paths that both lead up to the 'Wait for condition' and then to 'Create Event', and therefor both paths do trigger the event. The 'Wait for condition' itself does not check if it has already been triggered by another path, it will just fire.
To avoid this kind of behavior, either remove the path between 'Run Script' and 'Wait for condition'. Another thought would be to just have the first three steps in serial (i.e. why are you branching between 'Run Script' and 'Wait for condition'?).
Or, add a variable to your workflow that is set to 'True' by 'Create Event', and have 'Create Event' check if the variable is 'False' before actually firing the event.
Kind regards
Ralf Schnell, Senior Platform Evangelist
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2019 11:51 PM
Need more clarification on this,
This is my current workflow,
1.Accordingly after "create event: test form record producer eevent" activity is triggered twice with different sys_id s, the "create task" activity is also triggered twice but there is only one task created. If that is the case it should create two tasks. please provide clarification on the same.
2.There is two timer activity triggered with different sys_id s.After Killing one "Timer", if I try to kill other timer, it shows record not found, though it has different sys_id s. And it triggers the "create event :test for event after timer" activity twice.
Provide clarification on both the points.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2020 03:10 AM
Hi Anjali,
I am facing the same issue. Do you find any resolution for this issue.
In my workflow, there is an wait for condition activity which gets triggered twice by the two transition paths, So that the activities next to wait for condition are getting trigerred twice.
Pls let me know if you have any solution on this.
Thanks!
Ramkumar