# Limitations

> Common issues with Integration Service platform-level limits in Automation Suite, including the 8 MB maximum data processing limit affecting connectors and activities.

This section describes platform-level limits and other limitations that impact all
Integration Service connectors and/or activities.

## Data processing limits

Integration Service has a platform limit for retrieving responses. The maximum limit
for data processing is 8 MB. This means that, for some API calls, the number of
responses retrieved can exceed the 8 MB limit and throw the following error message:
"Response content too large".

:::note
The 8 MB limit applies to data in JSON format. This
includes cases where files are sent or received in a Base64 format as part of
the JSON data. For files handled outside of JSON, the limit is 1 GB.
:::

### Workaround

You can take the following steps to ensure the data processing limit is not
exceeded:

* Adjust the **Max records** field at activity level to a lower
  number.
* Add filtering to your queries. Providing filter parameters can limit the
  number of responses.

## Activity timeouts

There is a platform-wide timeout of 90 seconds for all activities and triggers based on Integration Service connectors. This means that if a response is not received from the API within 90 seconds, the activity fails with a timeout error.

## Trigger limitations

This section lists the known limitations of Integration Service triggers.

### Maximum record limit

#### Description

Integration Service triggers currently have a maximum limit of 1,000 records per
trigger execution. If a trigger attempts to retrieve more than 1,000 records within
the configured time interval (for example, one minute or five minutes) and the
vendor's system emits more records than this limit, any records exceeding the
threshold are not captured and may be lost.

#### Impact

This limitation may affect workflows or automations that require processing large
datasets, as the trigger may not retrieve all records.

#### Workaround

We are actively working to address this constraint. Until then, to minimize the
impact, you can configure the trigger interval to the minimum possible duration, as
explained in [Polling interval](https://docs.uipath.com/integration-service/automation-suite/2024.10/user-guide/triggers#polling-interval).
Increasing the frequency of trigger execution ensures that all records are captured
across multiple trigger runs.

### Auto-disabling triggers

If a trigger encounters 100 consecutive errors caused by issues in third-party
applications during polling for new or updated events, the system automatically
disables the trigger. This mechanism helps maintain system stability.

When one of your triggers is disabled, you will receive an email notification. You
must manually re-enable the trigger after the underlying issue causing the errors
has been fixed.

### Editing triggers

Editing an existing trigger is not currently supported. The only options for trigger
management are creating or deleting triggers. For any desired changes, you must
delete the existing trigger and add a new one.