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

[SumajRajNk]

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

[Ankur Bawiskar]

@SumajRajNk 

for older RITMs they should have workflow context associated to it

For new RITMs the flow will come into picture

did you not test this in DEV, QA?

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

[SumajRajNk]

Hi @Ankur Bawiskar 

I can see the same RITM in workflow context and flow context tables. Workflow context was created at the time of RITM created and flow context was created at the time of update made in the task/RITM(after moving the Flow Migration to PROD).

Regards,

Sumaj

[Ankur Bawiskar]

@SumajRajNk 

Sorry I didn't get

Consider you moved your update set on 14th April 10 AM IST.

So whichever RITMs raised before that were using workflow

Whichever RITMs were raised after 10am IST will use flow associated to that catalog item

I didn't get this line, what it means -> flow context was created at the time of update made in the task/RITM

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

[SumajRajNk]

@Ankur Bawiskar 

Yes new Flow is triggering for old RITMs which were raised before moving the update set. I mean that when we update anything in the task/RITM of previously generated ones with workflow, the new flow is triggering and generating new tasks/approvals sent to users again for old requests too.