Two SCTASk tickets are creating in a parallel but auto updating the state.

[LaraReddy]

HI All,

We created a Flow to generate two SCTASKs simultaneously, and it is working as expected. However, we observed an issue with the task states.

For example, if one SCTASK is closed as Closed Complete and the other is closed as Closed Incomplete, the RITM is correctly updated to Closed Incomplete based on the Flow logic. However, the state of the first SCTASK unexpectedly changes from Closed Complete to Closed Incomplete, and vice versa, causing both SCTASKs to end up with the same state.

Advance thanks.

[Sagar Pagar]

Hi @LaraReddy,

Have you checked the business rules on sc_req_item, sc_task tables which might be changing the states.

Thanks,

Sagar Pagar

[Ankur Bawiskar]

@LaraReddy 

any custom BR logic is doing this?

what debugging did you do?

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Lakshmi888888]

Hi @LaraReddy ,

Since the flow shown is only responsible for creating the two SCTASKs, the issue is likely occurring during task closure rather than task creation.

Normally, if one SCTASK is closed as Closed Complete and another as Closed Incomplete, the RITM can be updated based on your business logic, but the individual SCTASK states should remain unchanged.

I would recommend checking the following:

• Any Flows triggered on SCTASK or RITM updates that may be synchronizing task states.
• Business Rules on sc_task or sc_req_item that update child task states when the RITM state changes.
• Workflow activities (if using legacy workflows) that may be closing or updating related tasks.
• The Audit History (sys_audit) of the SCTASK whose state changes unexpectedly. This is usually the quickest way to identify what process, flow, or business rule updated the state.

As a test, review the audit history immediately after closing the second SCTASK and note what updates the first SCTASK from Closed Complete to Closed Incomplete (or vice versa).

[LaraReddy]

Thanks for the response.

We do have a OOB Business Rule called "Close Tasks Due to Cancellations", it's changing the state to closed incomplete.

Can we create a new BR not to conflict with OOB script OR is there any way we can stop the OOB BR execution at the existing flow level ?