We are currently testing our application for investment requests using Nintex Workflows. As part of the process, tasks are generated that include reminder notifications (e.g., after 3 days of inactivity).
We encountered a critical issue:
If a SharePoint list item is deleted after a task has been created for it, the task still exists in the Nintex system. When the reminder is triggered (e.g., after 3 days), the assigned user receives a reminder email with a link to the task. Since the user is unaware that the related item was deleted, they may open the task and approve it.
This leads to the workflow continuing execution as if the deleted item still exists. For example, it might notify another person that the request was finally approved — even though the actual request (the deleted list item) no longer exists.
This behavior can lead to serious process inconsistencies.
Idea/Request:
Could the reminder system include a validation step to check whether the associated SharePoint item still exists before sending out a reminder or allowing task interaction?
This could be implemented using a simple CAML query on the item ID:
<Query>
<Where>
<Eq>
<FieldRef Name="ID" />
<Value Type="Counter">150</Value>
</Eq>
</Where>
</Query>
This check would prevent unnecessary and potentially misleading reminders and help ensure workflow integrity. Without such a check, we are forced to manually ensure all workflows are properly terminated before deleting list items — which is error-prone and not always feasible in larger systems.
Thanks, Ronny
@Guest Can you confirm if you are referring to Nintex Workflow for O365 or the standalone Nintex Workflow product?