Best Practices for Managing Tasks on Closed and Cancelled Projects

Last Modified On: July 31, 2026

When managing projects and opportunities in Salesforce, tasks often represent the actions required to move work forward. However, as projects are completed, canceled, or placed on hold, related tasks may remain open and continue appearing in user task lists, reminders, and reports.
 

This guide provides recommended practices for automating task management based on the status of related records. By implementing simple automation rules, organizations can keep task lists focused on active work while maintaining a complete history of completed and canceled activities.
 

The recommendations in this guide help distinguish between tasks that were completed, tasks that are no longer required due to cancellation, and tasks that should remain open while work is temporarily paused.

Existing Data

Before implementing automation, existing open tasks associated with closed, canceled, or inactive records should be reviewed and cleaned up.
 

For a one-time cleanup, use Data Loader to perform a bulk update of existing tasks. This allows you to quickly update historical records based on your organization’s task management rules without requiring users to manually review and close individual tasks.

Automating Project Task Updates Based on Record Status

Once the initial cleanup is complete, we recommend implementing automation to manage future tasks automatically. This ensures that when a project, opportunity, or related record changes status, associated project tasks are updated consistently and do not continue appearing in user task lists, reminders, or reports when they are no longer actionable.

When designing the automation, consider whether project tasks should be marked as Completed, Canceled/Not Required, or left open based on the status of the related record.

• Closed (Completed/Closed Won, etc.) – Automatically update any remaining open tasks to Completed. Once the related record is complete, those outstanding tasks generally no longer require action and only add noise to users’ task lists and reports.
   
• Canceled – Rather than marking these tasks as Completed, use a separate status such as Canceled or Not Required. This makes it clear that the task was not completed; it simply became unnecessary because the parent record was canceled. You can also add a note in the Project Task description to provide additional context on why the task was canceled or is no longer required.
   

  Administrators can configure Canceled tasks to be treated as equivalent to Completed through Custom Settings. When a Project Task is updated to Canceled, the system will automatically set % Complete to 100%. This allows canceled tasks to be excluded from active work views while preserving them for historical reporting.
   

  Once configured, canceled tasks can be filtered out from list views and reports. Additionally, users can enable the Hide Completed toggle in Task Console to exclude canceled tasks from their active task view.

• On Hold – Since the work is expected to resume, it’s usually better to leave the task open. If reminder notifications become an issue, you could use automation (or a custom flag) to temporarily exclude these tasks from reminder processes until the related record is active again.
  
  Alternatively, you can create a custom Task Status value such as On Hold. This allows users to clearly identify tasks that are temporarily paused while preserving the task history. Once the status is available, you can configure list views, reports, and dashboards to filter out tasks with an On Hold status when displaying active work.