Skip to content
Back

Any way to increase Transaction limits on self hosted instance?

  • 0
  • 1
  • Self Hosted
Human Sean
19 Nov, 2025, 07:27

I need to batch create rows, 50,000 rows at once. I tried to combine create rows with transactions api in n8n, but I can only import 10,000 rows at most. Is there any way I can increase this limit, by setting enviroment variables or in settings?

TL;DR
There are limits on the number of rows you can push in a single operation due to transaction limits, which can't be increased with an environment variable. Batching inserts (e.g., 5k per chunk) and automating the loop can help avoid timing out. The transaction limit for operations is 100, so restructuring the workflow to process batches safely without hitting this limit is necessary. Feel free to reach out for assistance with setting this up properly.
19 Nov, 2025, 09:13

You’re running into n8n’s hard execution + payload limits that’s why you can’t push more than ~10,000 rows in a single operation. It’s not something you can increase with an environment variable; the workflow just becomes too heavy for one transaction. I can help you set this up properly by batching the inserts (e.g., 5k per chunk) and automating the loop so it still runs as one process without timing out. Quick question: where are you inserting the 50,000 rows (Airtable, Notion, DB, etc.)? That affects the best batching method.

19 Nov, 2025, 09:24

<@1367298667920228386> Thanks for replying, I use a webhook trigger to accept a excel file with 50000 rows in it, I use loop over items with the batch size of 100(the max amount we can create in one operation), then I stage each loop into one transaction, then I got this error: Transaction already has 100 operations, adding 1 would exceed the maximum of 100

19 Nov, 2025, 09:29

The error comes from the DB/transactions API itself each transaction is limited to 100 operations, so even if n8n loops correctly, the backend will reject anything above that. That’s why the 10k+ batches always fail. I can help you fix this by restructuring the workflow so each batch is processed safely without hitting the transaction limit, while still keeping the whole upload automated. If you want, feel free to message me and I’ll walk you through the setup or help you build it properly.

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more