Auto closing tasks

RE: Auto closing tasks

elvisb958752 — Tue, 21 Oct 2025 09:26:21 GMT

Yes, your solution seems about correct, about the last part, I just need the process to start on a timer, like u mention something that autoruns on a daily basis, without any user interaction. I see now that you can do that by simply setting up a timer to the start event of the process model. Thanks for your suggestion

RE: Auto closing tasks

venkatrea696188 — Fri, 17 Oct 2025 15:26:09 GMT

Correct me if i am wrong .You want to have a process model which needs to trigger on it's own and update the status as completed for any records/tasks which didn't have any updates for couple of days (I hope you have different PM's for user to update those)??

If that's the case, isn't it straight forward. Have a Schedular Process model which runs on daily base (it's up to you) which queries records based on updated time (get all the records which didn't get updated in last 2 days) and update the status and write it to DB.

[quote userid="302119" url="~/discussions/f/general/39852/auto-closing-tasks"] no action/button click[/quote]

This part is bit confusing to understand , button click that means we thought it's an input task so we will suggest exceptions. Could you explain more about your requirement (any screenshots would be helpful)

RE: Auto closing tasks

Harsha Sharma — Fri, 17 Oct 2025 11:24:28 GMT

If process has a task active then Exception path is the way to go!

You can configure Exception Path which basically times out the user input task. If user doesnt complete the task before Timer is triggered the system executes the Exception path. Generally I configure 1 hour timer and the exception path can have nodes (email/write records etc) followed by an End node

For your use case you can setup the write records node in the exception path which will update status to Completed and Ends the process.

If you dont have any active process and you want the system to change status to complete after few days depending on some value/status then you need to setup the process model as a Daily running batch job. Basically have the process get the cases you want to mark Complete and then update all the cases which fulfill the criteria. If on a given day no such cases are found process should end otherwise should update status and notify users as needed.

RE: Auto closing tasks

Shubham Aware — Fri, 17 Oct 2025 11:23:56 GMT

Add a parallel gateway after the user input task.
Path 1: Normal user completion.
Path 2: Timer event set to 2 days -> Script task updates status, writes records, sends email -> Terminate event.

This timer path will auto-complete the task without user interaction after 2 days, effectively handling timeout scenarios in parallel to user actions.

Explained it properly in this link
https://docs.appian.com/suite/help/25.3/Process_Node_and_Smart_Service_Properties.html#exceptions-tab

RE: Auto closing tasks

elvisb958752 — Fri, 17 Oct 2025 11:15:33 GMT

I understand, but I simply want the task to be completed without any user interaction. Correct me if I'm wrong, but the scenario you provided suggests that the user needs to instigate the process 1st before the exception rule takes place.

RE: Auto closing tasks

elvisb958752 — Fri, 17 Oct 2025 11:11:40 GMT

For this scenario to work it would need the user to click on the button action that triggers the process model, which is not what I want. And as it is explained on the link that you provided you cannot setup exceptions on events.

RE: Auto closing tasks

Shubham Aware — Fri, 17 Oct 2025 10:56:21 GMT

Use an escalation timer on the user input task to auto-complete and send the email after the set time.

Exceptions tab

RE: Auto closing tasks

Stefan Helzle — Fri, 17 Oct 2025 10:54:02 GMT

This is what exceptions in user input tasks are made for.

https://docs.appian.com/suite/help/25.3/Process_Node_and_Smart_Service_Properties.html#exceptions-tab