This article walks you through how to manage data collection limitations, specifically how to limit the number of transactions per account per platform.
Before proceeding, make sure you’ve already registered the relevant internal accounts.
1. Trigger Commit with maxTransactionLimit [Link to Postman]
Request:
{
"internalAccountIds": [],
"fromDate": "2024-01-01T00:00:00+00:00",
"toDate": "2025-07-27T00:00:00+00:00",
"commitId": "6b16a104-422a-2f68-bafd-b4634eafc801",
"internalAccountIdentifiers": ["sweat_validator.near"],
"assetsToCollect":["near_native"],
"maxTransactionLimit": 10
}
Use the maxTransactionLimit parameter to define the maximum number of transactions to collect in this data collection process.
Set it to -1 for unlimited transactions.
If no value is provided, the default limit is 300,000 transactions.
The limit applies per internal account. For example, if you specify four internal accounts in internalAccountIdentifiers, each one will be limited to 10 transactions.
If the transaction limit is exceeded, the task will pause and wait for user input—either from the TRES Customer Success team or the user.
The TRES team will notify the customer via email or Slack to request approval.
Alternatively, the user can update the transaction limit via API.
2. Trigger Parallel Commit + Max Transaction Limit [Link to Postman]
Request:
{
"commitId": "6b16a104-422a-2f68-bafd-b4634eafc801",
"maxTransactionLimit": 10
}
commitId: The UUID of the data collection session you want to update.
The update will apply to all internal accounts included in that session.
maxTransactionLimit: The new limit to apply.
Triggering this mutation will automatically resume the data collection from where it left off.
Important: Customers can choose to apply the new limit themselves (self-serve), or request that the TRES Customer Success team execute it on their behalf.