using conditions on the backlog

[Legacy User]

(applications manager  v9.0.1_hf1_28334_28643)

we have several process flow schedules that run every 5 minutes.  if an agent becomes unavailable or we have network issues we end up with 100's of stalled (pred wait) or aborted jobs overnight/weekend.  can we via conditions -
check the backlog and if the flow is already running (not aborted) then cancel? 
Or if the a flow is aborted within the last X minutes then cancel?

i tried the condition 'is running' but the chain is running (since it is itself).  I think we need to look into the backlog queue. can this be done via conditions? we have not written any appworx system level scripts yet.  we thought of using a file as a marker and not run new flows if the marker is there.  if the marker is older than X minutes then try again.  is this the best way?

[Steve Alberts]

check the backlog and if the flow is already running (not aborted) then cancel? 

Yes, our solution to this was to create a substitution variable that runs:

select case
    when count(so_module) > 1
      then 'Y'
      else 'N'
  end
from so_job_queue
where so_module = '{job}'

The cyclic jobs need to have 'single run' unchecked and if the variable resolves to 'Y', use a condition to set a skip status.

[EdwardKnowles609434]

What we have done for an Every 5 Minutes during the day process flow, is to uncheck the Single Run box on the General tab and then add a BEFORE JOB RUNNING condition that checks to see if the Process Flow is running and set the Skip Status to PROC-N-BKLOG.  You could also do the same condition before you set the Skip Status to send out a notification indicating that something is holding it up. Ed. Ed Knowles                                                                                                         Email: [e-mail]<mailto> Assistant Director, IT                                                                                      Phone: [phone] Production Control & Enterprise Reporting ITS - Southern Illinois University Edwardsville From: Shilpa Enugala <automicsoftware> Sent: Wednesday, March 28, 2018 9:10 AM To: Knowles, Edward <eknowle> Subject: [Automic Community] using conditions on the backlog [Automic Community]<https></https> ________________________________ Shilpa Enugala started a new discussion: using conditions on the backlog (applications manager  v9.0.1_hf1_28334_28643) we have several process flow schedules that run every 5 minutes.  if an agent becomes unavailable or we have network issues we end up with 100's of stalled (pred wait) or aborted jobs overnight/weekend.  can we via conditions - check the backlog and if the flow is already running (not aborted) then cancel? Or if the a flow is aborted within the last X minutes then cancel? i tried the condition 'is running' but the chain is running (since it is itself).  I think we need to look into the backlog queue. can this be done via conditions? we have not written any appworx system level scripts yet.  we thought of using a file as a marker and not run new flows if the marker is there.  if the marker is older than X minutes then try again.  is this the best way?</eknowle></automicsoftware></mailto>

[Legacy User]

thanks, we will experiment some more.