subflow not allowing me to publish

MohammedA601527
Tera Contributor

Hi All,

 

I have a requirement to create a flow for the send an email when SLA breaches to 80%, 100%,120% and 140%.

 

We created a very long flow it is about 300 line flow because of this facing performance issues in the system.

 

so decided to use subflows in the sub flow while creating for 80% SLA breach we are using SLA percentage timer and trigger condition is on main FLOW so while publishing the subflow it is throwing an error like:  "SLA Percentage Timer can only be used when Trigger is SLA Task"

how to over come this please provide your inputs/suggestions thanknyou!

 

Looking forward for your response

 

Regards,

AK

11 REPLIES 11

@MohammedA601527 

it's a platform behavior.

If you are using "SLA Percentage Timer" flow action then the trigger should be SLA Task.

You need to use that only in Flow and cannot use in Subflow

SLA Percentage Timer action 

AnkurBawiskar_0-1751380537683.png

 

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

If your flow is too complex, then you can have one Flow for 80 %, another flow for 100, 120 and 140 %, all of them would be calling the subflow, but the sla percentage timer would be on the flow level

EDIT: one flow would be sufficient, and the checks for the thresholds would be similar to these:

KamilTEL_0-1751380831256.png

 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Hi  @GlideFather 

 

Thank you for the response, How to attach multiple flows in a single SLA definition, could you please help me with this 

 

Regards,

Ak

It was my original idea but then I realised it is not necessary.

It would be something like

  • Flow1: Wait until the SLA Definition is 80 %, then <flow executed>,
  • Flow2: Wait until the SLA Definition is 100 %, then <flow executed>,
  • Flow3: Wait until the SLA Definition is 120 %, then <flow executed>,
  • Flow4: Wait until the SLA Definition is 140 %, then <flow executed>,

But all the steps from <flow executed> could be the part of the subflow.

And instead - there would be one main Flow:

  • Condition 1: Wait until the SLA is 80 % > call subflow,
  • Condition 2: Wait until the SLA is 100 % > call subflow,
  • Condition 3: Wait until the SLA is 120 % > call subflow,
  • Condition 4: Wait until the SLA is 140 % > call subflow.

Does it make sense? How many steps/actions are done when one of the thresholds are reached? Is it sending some emails, triggering some creations, or what happens? Is it always the same step or it differs?

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Do you have any solution for this?