Skip to main content
To ensure fair use of our cloud resources, we have implemented a number of limits. If you use a self-hosted version of Membrane, you can change any of these limits by providing corresponding environment variables. Note: All limits are applied on a rolling window basis, meaning usage is continuously measured over time rather than resetting at fixed intervals.

​
API

  • If you need to work with larger data, please check Files.
  • If you need to run longer requests, use Flows.

​
Flow Runs

​
Understanding flow run queue limits

The flow run queue size per connection limit controls how many flow runs can be queued for a single connection before new flow runs are rejected with a rate limit error. Important architectural consideration: Simply increasing the queue size limit does not solve throughput issues. If your queue is consistently reaching the limit, it means flow runs are being queued faster than they can be processed. Increasing the queue size will only postpone the problem, not resolve it. To address high-volume flow processing:
  • Increase parallel flow runs per connection to process flows faster.
  • Optimize flow logic to reduce execution time.
The queue size limit exists to prevent memory issues and provide early feedback when your system cannot keep up with the incoming load.

​
External Event Pulls

​
Action