Technical Workflow - Auto Recovery | Community
Skip to main content
Ken_Qrious
Ken_Qrious
Level 4
November 4, 2021
Solved

Technical Workflow - Auto Recovery

  • November 4, 2021
  • 1 reply
  • 1501 views

I have created a utility workflow which monitors specific technical work flows to ensure they are running normally.  If a work flow which should be running but isn't is found the following are executed to stop and restart it (using java script)

 

xtk.workflow.Stop(strId)
xtk.workflow.Start(strId)

The problem is that if the job has a scheduler it will wait until it's next scheduled start, what I need is a way to "Execute Pending Task Now" so that the job restarts immediately.  I can see xtk:worflow methods for wakeup which looks like it might be want but I can't get it to start right away.

 

Is there away to start the workflow so that it runs immediately?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Darren_Bowers

    Hi @ken_qrious - there are a few ways to achieve this. I've found the simplest is to add an External signal to the start of the workflow and use xtk.workflow.PostEvent to kick it off via the External signal activity. This gives you the scheduler which will kick off when the schedule arrives, plus it also gives you a way to execute the workflow at any other time (once the workflow is running).

    Cheers

    Darren

    1 reply

    Darren_Bowers
    Darren_BowersAccepted solution
    Level 9
    November 4, 2021

    Hi @ken_qrious - there are a few ways to achieve this. I've found the simplest is to add an External signal to the start of the workflow and use xtk.workflow.PostEvent to kick it off via the External signal activity. This gives you the scheduler which will kick off when the schedule arrives, plus it also gives you a way to execute the workflow at any other time (once the workflow is running).

    Cheers

    Darren

      LaurentLam
      LaurentLam
      Level 5
      November 7, 2021

      Perfect answer, but carefull with this kind of methodology:
      Root cause of the issue should always be addressed in priority...
      I remember a customer that made in the past a such mechanism (but for none OOTB workflows) despite support recommandation: he burned in 5 monthes his xtkNewId sequence

        Ken_Qrious
        Ken_QriousAuthor
        Level 4
        November 8, 2021

        Thanks for the replies @darren_bowers and @laurentlam, it's good to be aware of potential pitfalls.  The main use for the auto restart would be for technical work flows which load data from external systems.  The process would be limited to selected work flows and would generate an alert to our support team.  

        Terms & ConditionsAccessibility statement

        Loading footer...