#graphql api Limit reached (100 tokens per 60000 ms)

1 messages · Page 1 of 1 (latest)

loud pecan
#

graphql api access "errors": "message": "Limit reached (100 tokens per 60000 ms)","LIMIT_REACHED",

atomic archBOT
#
Searched GraphQL API rate limit tokens LIMIT_REACHED
Found 10 results
#

You're hitting the API rate limit. Twenty enforces 100 requests per minute for API calls.

The error LIMIT_REACHED with "100 tokens per 60000 ms" means you've exceeded this threshold.

Quick fixes:

  1. Add delays between requests — minimum 600ms between calls for sustained usage
  2. Use batch operations — process up to 60 records per API call instead of individual requests
  3. Implement exponential backoff — when you get a 429 response, wait and retry with increasing delays

Example approach:

// Instead of 100 individual calls, batch 60 records per call
// This gives you ~6,000 records/minute throughput

If you're doing a large import, plan for approximately 17 minutes per 100,000 records at maximum throughput. Add buffer time for error handling and retries.

Let me know if you need help structuring your batch requests or implementing rate limit handling.

loud pecan
#

is there an admin env var RATE_LIMITING

atomic archBOT
#
Searched rate limiting environment variable admin configuration
Found 10 results
#

Yes, there are environment variables to configure rate limiting in Twenty.

Rate limiting configuration variables:

You can configure these through the Admin Panel (Settings → Admin Panel → Configuration Variables) or via .env file:

+--------------------------------+-----------------------------------+
|            Variable            |            Description            |
+--------------------------------+-----------------------------------+
| `WORKFLOW_EXEC_THROTTLE_LIMIT` | Workflow execution throttle limit |
| `WORKFLOW_EXEC_THROTTLE_TTL`   | Workflow execution throttle TTL   |
+--------------------------------+-----------------------------------+

The default API rate limit is 100 requests per 60,000ms (1 minute).

If you're self-hosting, you can adjust rate limiting settings through the admin panel configuration. Look for the Workflow & Rate Limiting section in your configuration variables.

Note: Some configuration requires IS_CONFIG_VARIABLES_IN_DB_ENABLED=true (the default) to modify via the admin panel. If you've set IS_CONFIG_VARIABLES_IN_DB_ENABLED=false, you'll need to add these variables to your .env file instead.

For the complete list of configurable variables, check the config-variables.ts source file.

These pages may help:

Twenty Documentation
Setup - Twenty Documentation
Twenty Documentation
Import Data via API - Twenty Documentation

When and how to use Twenty's APIs for large-scale data imports.

loud pecan
#

explain me its default values

atomic archBOT
#
Searched rate limiting default values configuration environment variables
Found 10 results
#
Searched WORKFLOW_EXEC_THROTTLE_LIMIT WORKFLOW_EXEC_THROTTLE_TTL default value throttle
Found 10 results
#

Based on the documentation, I can see that WORKFLOW_EXEC_THROTTLE_LIMIT and WORKFLOW_EXEC_THROTTLE_TTL were added in v0.40.0, but the documentation does not specify their exact default values.

The documentation mentions these variables exist for Workflow & Rate Limiting configuration, but the specific default values are not documented in the pages I found.

For the API rate limit you're hitting, the default is:

  • 100 requests per 60,000ms (1 minute)

For the workflow execution throttle variables (WORKFLOW_EXEC_THROTTLE_LIMIT and WORKFLOW_EXEC_THROTTLE_TTL), the default values are not explicitly documented. To find the exact defaults, you would need to check the config-variables.ts source file directly.

To view or modify these values:

  1. Go to Settings → Admin Panel → Configuration Variables
  2. Look for the Workflow & Rate Limiting section
  3. The current values (including defaults) will be displayed there

If you're self-hosting and need to increase limits, you can adjust these values through the admin panel (if IS_CONFIG_VARIABLES_IN_DB_ENABLED=true) or via your .env file.

GitHub
twenty/packages/twenty-server/src/engine/core-modules/twenty-config...

Building a modern alternative to Salesforce, powered by the community. - twentyhq/twenty

loud pecan
#

can i set API_RATE_LIMITING_SHORT_LIMIT = 100;

atomic archBOT
#
Searched API_RATE_LIMITING_SHORT_LIMIT environment variable configuration
Found 10 results