Resolving task character limit errors

Last updated: October 3, 2025

Overview

When attempting to close tasks with large amounts of text in comments or descriptions, you may encounter a character limit error. This article explains how to resolve these errors using either the Task Audit Trail feature or temporary bypass settings.

Process

Using Task Audit Trail

The Task Audit Trail feature provides a way to track task updates while avoiding character limit issues. When enabled, comments are stored in a separate object, allowing for better management of large text entries.

  1. Navigate to the task record

  2. To the right of the Related tab, locate the Audit Trail tab

  3. All task updates and changes will be recorded here, including comments

Temporarily bypassing character limits

For occasional situations where you need to close a task that exceeds the character limit, follow these steps:

  1. Navigate to Setup

  2. In Quick Find, search for Custom Settings

  3. Click Manage on Veruna Support, then Edit

  4. Type "true" in both the "Task Audit Trail Bypass" and "Task Prevent Deletion Bypass" fields

  5. Save the changes

  6. Navigate to the task and mark it as Completed

  7. Return to Veruna Custom Settings

  8. Delete "true" from both fields and save

Considerations

  • The standard Salesforce character limit for tasks is 30,000 characters

  • Task Audit Trail creates a permanent record of all updates and changes made to a task

  • Each entry in the Audit Trail includes the date, time, and user who made the change

  • The bypass settings should only be used temporarily when needed to close specific tasks with characters greater than 30,000 characters

  • If the Task Audit Trail feature isn't turned on in your org, reach out to amplo support to turn this on

Troubleshooting

If you continue to experience character limit errors after enabling Task Audit Trail:

  • Verify with amplo support that the migration script has been run to move existing comments to the new Audit Trail object

  • Check if there are any integrations or automated processes creating duplicate comments

  • Consider adjusting any integrations to use the new Audit Trail system instead of the standard description field