Managing concurrency

Limit the number of concurrently running steps for your function with the concurrency configuration options. Setting an optional key parameter limits the concurrency for each unique value of the expression.

export default inngest.createFunction(
  {
    id: "sync-contacts",
    concurrency: {
      limit: 10,
    },
  }
  // ...
);

Setting concurrency limits are very useful for:

• Handling API rate limits - Limit concurrency to stay within the rate limit quotas that are allowed by a given third party API.
• Limiting database operations or connections
• Preventing one of your user's accounts from consuming too many resources (see key)

Alternatively, if you want to limit the number of times that your function runs in a given period, the rateLimit option may be better for your use case.

How concurrency works

Traditional queue and worker architectures require you to specify the number of concurrently processed messages by adding or removing worker processes that poll for messages. As Inngest executes your functions via HTTP, concurrency is managed by Inngest itself, ensuring that you can control the number of HTTP requests sent to your application.

Internally, Inngest creates a queue for each of your functions in order to execute steps efficiently. Each step to be executed is added to a given function's internal queue and setting a concurrency limit instructs Inngest to only process and execute a certain number of these steps concurrently.

Limiting concurrency for a specific key

Optionally, specifying a concurrency key applies the limit to unique values of your key expression. This is useful to limit throughput of a function for particular subsets of your events. In essence, this creates a "sub-queue" for each unique key (e.g. a limit of 2 concurrent steps processed for each event.data.customer_id).

Configuration

Examples

Handling third party API rate limits

Here, we use the Resend SDK to send an email. Resend's rate limit is 10 requests per second so we set a lower concurrency as our function is simple and may execute multiple times per second. Here we use a limit of 4 to keep the throughput a bit slower than necessary:

export const send = inngest.createFunction(
  {
    name: "Email: Pending invoice",
    id: "email-pending-invoice",
    concurrency: {
      limit: 4, // Resend's rate limit is 10 req/s
    },
  },
  { event: "billing/invoice.pending" },
  async ({ event, step }) => {
    await step.run("send-email", async () => {
      return await resend.sendEmail({
        from: "hello@myco.com",
        to: event.user.email,
        subject: `Invoice pending for ${event.data.invoicePeriod}`,
        text: `Dear user, ...`,
      });
    });

    return { message: "success" };
  }
);

Restricting parallel import jobs for a customer id

In this hypothetical system, customers can upload .csv files which each need to be processed and imported. We want to limit each customer to only one import job at a time so no two jobs are writing to a customer's data at a given time. We do this by setting a limit: 1 and a concurrency key to the customerId which is included in every single event payload.

Inngest ensures that the concurrency (1) applies to each unique value for event.data.customerId. This allows different customers to have functions running at the same exact time, but no given customer can have two functions running at once!

export const send = inngest.createFunction(
  {
    name: "Process customer csv import",
    id: "process-customer-csv-import",
    concurrency: {
      limit: 1,
      key: `event.data.customerId`, // You can use any piece of data from the event payload
    },
  },
  { event: "csv/file.uploaded" },
  async ({ event, step }) => {
    await step.run("process-file", async () => {
      const file = await bucket.fetch(event.data.fileURI);
      // ...
    });

    return { message: "success" };
  }
);

Limits

The maximum possible concurrency that can be set is based on your plan.

• Free: 25
• Team: 100
• Startup: 500
• Enterprise: Up to 20,000 contact us