Duplicate tasks getting generated for same RITMs after migrating from workflow to Flow

SumajRajNk
Tera Contributor

Hi Team

 

The workflow attached to a catalog item in PRODUCTION was migrated to FLOW... Now duplicate Tasks are getting generated for already generated RITMs which got generated previously at the time when Process Engine was not migrated to Flow i.e. when it was in workflow!

 

What would be the reason behind this? How can I solve this? Solutions for this issue are highly appreciated!

#flow #workflow #tasks #catalogitem

12 REPLIES 12

@SumajRajNk 

then that's the reason. for older RITMs tasks got created due to workflow and since flow also got associated new tasks got created again.

how is the new flow configured and why it's running for older RITMs?

Flow on service catalog trigger only runs when fresh RITM is raised and not when it's updated.

Are you making this flow trigger explicitly via some script for older RITMs?

if yes then I won't recommend this.

Let the older RITMs follow the workflow and reach the end

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

@Ankur Bawiskar 

I don't know why it's running for older RITMs ! Also how can I check if flow trigger explicitly via some script for older RITMs?

@SumajRajNk 

Please answer this question

1) how is the new flow configured? is it configured to run on "Service Catalog Trigger"

2) search in any business rule that flow is getting called with script contains the flow name

Also did you not test this in DEV or QA?

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

@Ankur Bawiskar 

Hi it is Service Catalog Trigger itself

I haven't tested in DEV & QA

I didn't understood your 2nd point

@SumajRajNk 

If it was not tested in DEV and QA then why it was moved to PROD? Not an ideal way

Ideally the flow should not be triggered from script and should be triggering only on RITM creation

Search in business rule table like this, do similar in script include

AnkurBawiskar_0-1744717910918.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