đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
When assigning a task in Nintex Automation Cloud, you have the option to set an escalation date. If the task isn't completed by that date, it escalates to another user. However, after escalation, the task’s due date is automatically extended by an additional 360 days, regardless of the reason.
The purpose of task escalation is to ensure timely completion and prevent tasks from being overlooked. Extending the due date by 360 days after escalation completely undermines this goal, as it becomes impossible to track whether the task is overdue. In addition, no additional reminders are sent to either the original assignee or the new assignee after escalation, which often results in tasks being forgotten. This issue is further exacerbated by the Nintex "My Tasks" view, which only displays tasks assigned within the last 30 days, making it even harder to track overdue tasks.
Based on our understanding of the API behavior and feedback from Nintex Support, the due date also serves as the task’s technical expiration date, after which the task is no longer available (Which seems to be the reason for this stupid 360 day extension). Ideally, the due date and expiration date should be treated as two separate properties to improve task tracking and management.
It is mind-boggling that this feature is not currently available on a platform of this scale. We kindly request that this be addressed in a future release, as managing tasks at scale in Nintex Automation Cloud is currently a significant challenge. A solution to this issue would greatly improve the platform’s overall usability for larger-scale task management.
I strongly support this proposal. The current behavior of extending the due date by 360 days after escalation introduces significant challenges for task management and accountability. Escalation should reinforce urgency, not dilute it. By conflating the due date with the technical expiration date, the system undermines the core purpose of escalation and makes overdue tracking nearly impossible.
Separating due date (for business logic and visibility) from expiration date (for technical lifecycle) is a best-practice approach that would greatly improve usability and transparency. Additionally, implementing post-escalation reminders for both the original and new assignee would ensure tasks remain visible and actionable.
This change would align Nintex Automation Cloud with enterprise-grade task management expectations and significantly enhance its reliability for large-scale operations. I highly recommend prioritizing this improvement in an upcoming release.