In workflow is it a best practice, if a "End" activity get cancelled

[Lavanya D]

Hi All,

I have a requirement , that after creating a catalog task where we need to check as whether we get any "Additional comment" from user or else it should wait for 7 days and should trigger a notification to the user.

So in the workflow I am using a Branch after creating a catalog task and either the branch will check, as whether the task got "Closed Complete" (this update happens in BR, by checking as whether we are getting any comments from user) OR it will wait for 7 days Timer (so having 2 path). I am not using "Join" activity as it will wait for both the path to complete. So I have a "If" condition check for joining both the path so either the task to "Close Complete" or remaining in previous state.

Flow working is good and as expected. As either of a path will get succeed , while the other path will be cancelled. So the "End" activity is also getting cancelled once after the flow is complete.

My Query is , whether is it a Best Practice, that the "End" activity is getting Cancelled for a flow. I don't find any other way to do this checking for 2 conditions at a stage, where after 7 days if still comment is not updated, I need to wait for another 14 days by sending a custom Notification to user. And this custom Notification creation I should do it only from Workflow, should not create in table level notification.

Please suggest me as whether this will be a good practice or suggest me a solution.

[Brad Bowman · Accepted solution]

That's absolutely fine for an End activity to show as cancelled, as long as all of the paths are working as you want them too.  You're setting the RITM closed complete when it ends normally, which is more important.  The workflow being cancelled shouldn't even show up on any reports, or lead to any confusion.

[Lavanya D]

Thank you, yes the path is completing as expected and I am also setting the RITM to Close Complete.