What is the condition on this rule? Do you have several records it would run on?
Does it run several times for the same record?
yes it does runs several times for the same record
I saw that happening on rules running on "UPDATE" event. For example when I was changing a task status.
The problem was I was triggering a process through the rule, and the process modified the same task record, so the rule fired again...
I had to put a condition in the rule to only fire the rule when the task had a specific status.
Yes, that's right.
But my trigger event is timer type, so it is time based.
I tried it many times, but had no luck.
Ok my question is this, does the rule runs two / three times for all the records (this would be a problem) or does it run 1 time for each record instance?
The behavior is different than an escalation in ARS, it should fire for each record instance now.
Rule trigger the process,
And process consists of multi-instance loop.
Process creates a new record instance for every record instance of another record.
When the trigger type is RECORD EVENT, task executes normally(It creates single record instance for every record instance of another record).
And for trigger type TIMER EVENT, Process creates 4 record instances for every record instance.
I think the problem is with TIMER EVENT TRIGGER TYPE.
I have been referring with many people, but none of them were able to solve the problem.
1 of 1 people found this helpful
It seems you are BMC internal, can you reach out to me on Skype or by email and share your environment?