How to let a workflow to run again if condition matches again?

[Zod]

Hi Experts,

as we not yet using event management - we at least want be notified if our MID Servers are down.

I created a WF to create an incident in case status changes to 'Down' ... .

Unfortunately the Wf only runs once. If the status is up again and switches back to down ... no new Incident will be opened.

How can I re-run the wf if condition is true again?

I'd like to avoid fancy business rule deleting workflow version and restarting the wf hardcoded ... . The must be an option to tell within the workflow that it has to run again ... .

I was assuming I can just cancel the workflow after incident has been created ... but it will not run gain, even if cancelled.

What to do?

[Michael Fry1]

yes

[samuelscott]

I fixed it Micheal!! You were extremely helpful...I appreciate it!

[Rumija Padhy]

Hi,

I have a similar issue. I want my WF to run multiple times when the condition met. When i checked "Run Multiple" field it really triggers the WF mutiple times by deleting the old one (i don't need to explicitly delete the WF using business rule.) But the problem is when the WF is waiting for the approval (inflight approvals) and any update happens on the table record. the WF triggers again by deleting the inflight WF.

I don't want the WF to get trigger when it is already waiting for approval when there is a update happens on the parent record.

Appreciate if you can provide some input to this.

[samuelscott]

Ok...I was looking for that workflow in the company's development instance, I have a personal developer instance and now I've found it. 

The difference with that workflow is that it starts from the begining of the process, mine start midway through the process (which works with UI actions and business rules), whenever the stage is "Awaiting CX SDM/P&IT Approval". A screenshot of the trigger is shown below

Also, I should mention that the change of stage is caused by a UI action that is from a table that IS NOT configured to my workflow. When the approval is rejected, the following run script activity created a new record in the related table I'm mentioning, forcing the process to the previous step and to click on the ui action that re-triggers my workflow.

I hope I'm clear...