Action Required: Mandatory Salesforce Sites security configuration update

Sorry, we didn't find any relevant articles for you.

Send us your queries using the form below and we will get back to you with a solution.

Why am I getting the error Gift Transaction Id: data value too large?

Overview

This article explains the cause and resolution for the Gift Transaction Id: data value too large error that may appear in the Error Logs within Payments2Us.

The error commonly appears as:

Program Area: paymentTxnExtShareLockProcessor.paymentLock
Subject: Gift Transaction Id
Description: data value too large: xxxxxxxxxxxxxxxxxx} (max
length=18)

The log lists multiple Payment Transactions with the above message. 

 

What the Error Means

The error typically occurs when a flow or automation passes an invalid Gift Transaction ID—for example, including an extra character such as a closing brace (})—causing it to exceed Salesforce’s maximum 18-character ID length limit.

Gift Transaction Id: data value too large: [ID] (max length=18)

This usually occurs when:

  • A flow was created where the Gift transaction ID is passed

 

Causes:

  • Custom flows or automations inserting or updating the Gift Transaction ID field with malformed values.
  • Conditional flows that trigger inconsistently, explaining why resetting the Payment Txn can sometimes bypass the issue.
    To confirm, temporarily disable custom flows affecting Gift Transactions or Payment Txns and re-test.

 

  1. Review Flows and Automations:
    • Check any custom Flows, Process Builders, or triggers updating Gift Transaction IDs.
    • Look for cases where an extra character or symbol is being appended to the record ID.
  2. Test by Disabling Flows:
    • Temporarily disable relevant flows and reprocess the transaction to confirm the source.
  3. Validate Field Values:
    • Ensure that all Gift Transaction IDs being passed are exactly 18 characters.
    • Remove any stray braces or formatting characters.
  4. Reprocess Transactions:
    • Once corrected, reset the affected Payment Txn Status to NPC Processing Start and re-run NPC Processing.

 

 

Updated at November 11th, 2025

Was this article helpful?