Need some help understanding the connection between events, workflows and limits

[ovizii]

I created an event A with a target group and algorithm: random and the limits of: max jobs: 1, max queue: 0 and max retries: 0

Next I created a workflow A which runs on a daily schedule with the limits of: max jobs: 1, max queue: 0 and max retries: 0. I then added a multiplexer with a stagger delay of 30 seconds, so the jobs don't all start at the same time. The multiplexer then attaches to event A, but has two limiters attached: max jobs: 5 and max queue: 10.

Now the last time workflow A ran, one of the jobs took longer then 30 seconds and when the next one started staggered I got the error of:

Job Aborted: Maximum number of concurrent jobs for event has been reached.

I am now wondering what I did wrong and which settings to correct. I assumed the limiters attached to the event in the workflow would override the limiters of the event?

[jhuckaby]

Ah, sorry for the confusion. Here is the explanation:

When you assign a limit to an event, that limit is ALWAYS going to be there, even if you use the event in a workflow. All limits come "in tow" with their respective events into workflows.

When you attach limit nodes to event nodes in a workflow, those are APPENDED to the list of limits for that event. Same with action nodes (they append to any actions already assigned to the event).

Also note that events can automatically inherit limits and actions from their assigned categories, and those come in tow as well.

So in your case, the limit that triggers first takes precedence (i.e. your max jobs of 1 assigned to event A). This applies even in a workflow.

I cover this in my latest video, if you are interested in watching: https://www.youtube.com/watch?v=UVq6fo0njh0

I will work on somehow making this more clear in the UI.

[ovizii]

Thanks. Going to watch that video now. Most things have become clear, but I have a new question:

If I have an event, which only exists so it can be used in a workflow and never on its own, is it safe to disable:

• any limits
• any triggers
• any actions

since those will be defined in the workflow which then uses this event?

Bonus question:
When editing the workflow which uses this event, at the top, there are “Workflow Limits” defined for max jobs, queue, and retries.
In the visual workflow editor below, I can also add limiters. Which ones do take precedence?

[jhuckaby]

If I have an event, which only exists so it can be used in a workflow and never on its own, is it safe to disable: any limits, any triggers, any actions, since those will be defined in the workflow which then uses this event?

100% correct. You got it.

Bonus question: When editing the workflow which uses this event, at the top, there are “Workflow Limits” defined for max jobs, queue, and retries. In the visual workflow editor below, I can also add limiters. Which ones do take precedence?

This is covered completely in the video 😊 , but I'll answer it here as well:

The "Workflow Limits" and "Workflow Actions" defined above the workflow editor apply to the workflow parent job only, and are not inherited by sub-jobs. For e.g. if you add a Max Concurrent Jobs limit and set it to 1, it means that you only want 1 WORKFLOW running at once. It has no governance on the jobs INSIDE the workflow, if that makes any sense. Likewise, if you add a "Workflow Action" to send an email on success, that means it will only send the email with the entire workflow completes, not any jobs inside it.

Each running workflow itself is a job, so those limits / actions govern the workflow job itself, not the sub-jobs it launches.

I hope this makes sense.

Enjoy the video!

[ovizii]

Haha, indeed you explain that right in the second minute. Thanks!

P.S. I now finally know how to pronounce xyOps ;-)