Closure Of Asset Reclamation Request with Usage Of Flow

[priyanshp4]

Dear Community,

I am seeking here for some help; I have to mark multiple new/in progress ARR's as closed skipped based on certain requirements in my org with the help of flow.

Scenario: ARR have its sub-requests that is hardware and software, now this also have several task.

--> In order to close this hierarchy I am marking all present hardware task as closed incomplete and hardware request line will automatically becomes as closed skipped 

--> For software tasks , am marking them as closed incomplete and software request line as cancelled, because its status is not automatically getting changed because in some scenarios there are no task present

--> Now finally i am making ARR as closed skipped.

I want to understand is it the right approach i am using to mark as closed skipped? because once i mark it as closed skipped, seems there is some backend thing running which makes status as completed with error.

Thanks,,

[sachinvic · Accepted solution]

@priyanshp4 

Hi,

The approach depends on the OOTB flow that controls the ARR >> Request Line >> Task hierarchy. Instead of manually setting each record to Closed Skipped, first check what happens when the hardware/software tasks are completed or cancelled.

You can verify this by:

1. Open the ARR Flow/Flow Designer configuration and check the actions triggered when a task or request line is closed.
2. Check the Business Rules/Flows on the ARR and request-line tables that update the parent status.
3. Test the scenarios separately:
   • Hardware task >> Closed Incomplete >> Hardware request line
   • Software task >> Closed Incomplete/Cancelled >> Software request line
   • No task >> Request line cancellation
   • Finally >> ARR >> Closed Skipped
4. Check the System Logs/Flow execution details to identify which automation is changing the status.

If the OOTB automation is designed to cascade these statuses, avoid adding another script just to force Closed Skipped, as that can result in conflicting updates or unexpected completion states.

If the status is still changing incorrectly after the expected child records are updated, the next step is to identify the specific Flow/Business Rule making the update rather than adding a delay or hard-coded status change.

Helpful? Please mark the response as Accepted Solution ✅ and close the thread — it helps others find the solution faster.

Regards,
Sachinvic
✨ ArchX Certified | 16x ServiceNow AI MVP