Feedback for this Doc

[Ziweil6]

User would face the issue when setting "User Property", showed copy activity success but pipeline do not finish. Actually it hits the error request size too large when sending requests to monitoring metadata service: Cosmos DB. Would it possible to write it clear how much data would hit the error or how to self-mitigate in the Doc to guide customer who face the issue in the future.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 5f8f06db-58d4-75b9-f150-9a1b4767cf75
• Version Independent ID: 54c26e53-460a-2f6e-b4f2-86f1e8581435
• Content: Copy activity - Azure Data Factory & Azure Synapse
• Content Source: articles/data-factory/copy-activity-overview.md
• Service: data-factory
• Sub-service: data-movement
• GitHub Login: @jianleishen
• Microsoft Alias: jianleishen

[GiftA-MSFT]

@Ziweil6 we'll review your feedback and get back to you shortly. Thanks.

[himanshusinha-msft]

Hello @Ziweil6 ,
I think this is called out here https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-cosmos-db?tabs=data-factory . The pase you are refering to is the "main" copy activity and then we have links to different connectors on this pase . of you click on the "Azure cosmosDB" it does navigate to the page which I refered .

"Cosmos DB limits single request's size to 2MB. The formula is Request Size = Single Document Size * Write Batch Size. If you hit error saying "Request size is too large.", reduce the writeBatchSize value in copy sink configuration."

We are closing this issue now , you can always re-open the issue if you think that appropriate .