Skip to content

Quotas & Rate Limits

DIBOP applies quotas and rate limits to ensure fair usage, protect external systems, and maintain platform stability. This page explains what limits apply and how to manage them.

Types of Limits

API Call Quotas

API call quotas limit the total number of API calls your enterprise can make to external systems within a billing period (typically monthly).

Tier Monthly API Call Quota
Starter 10,000
Professional 100,000
Enterprise Custom (negotiated)

Quota Scope

The quota applies to calls made by DIBOP to external systems, not to calls made to the DIBOP API itself. Internal DIBOP API calls (e.g., loading the dashboard, browsing orchestrations) do not count against your quota.

Orchestration Execution Limits

Limits on the number of orchestration executions per month:

Tier Monthly Executions
Starter 5,000
Professional 50,000
Enterprise Custom

Rate Limits

Rate limits restrict the number of requests per second or per minute, preventing sudden bursts from overwhelming external systems.

Scope Default Rate Limit
Per enterprise, per system 60 requests/minute
Per enterprise, total 300 requests/minute
Per orchestration 30 requests/minute

Rate limits are applied per enterprise. Different enterprises on the platform have independent rate limits.

Storage Quotas

Limits on the amount of data stored:

Data Type Default Quota
Execution logs 10 GB
API call logs 20 GB
Canonical data records 5 GB
Dead letter queue 2 GB

Monitoring Your Usage

Current Usage

View your current usage from SETTINGS > Enterprise Settings or from the Platform Metrics page:

  • API calls used vs quota (with percentage)
  • Orchestration executions used vs limit
  • Storage used vs quota (per category)

Usage Trend

The Platform Metrics page shows your usage over time, helping you predict when you might approach a limit:

  • Daily API call volume chart
  • Projected usage based on the current trend
  • Days remaining in the billing period

Usage Alerts

Set up alert rules to be notified when approaching limits:

  1. Navigate to MONITOR > Alert Rules
  2. Create a rule with type Usage Threshold
  3. Configure:
    • Metric: API Call Quota, Execution Limit, or Storage Quota
    • Threshold: Percentage of limit (e.g., 80%)
    • Notification channel: Email, webhook, or Slack

Set Multiple Thresholds

Create alerts at 80% and 95% of your quota. The first gives you time to plan; the second is an urgent warning.

What Happens When You Hit a Limit

API Call Quota Exceeded

When your enterprise exhausts its monthly API call quota:

  • New orchestration executions that require API calls will fail at the first API call step
  • The error message will indicate "API call quota exceeded"
  • Orchestrations already in progress may complete (quota is checked at step execution, not at orchestration start)
  • Manual API calls from the Test Runner will also fail
  • The quota resets at the start of the next billing period

Execution Limit Exceeded

When your enterprise exhausts its monthly execution limit:

  • New orchestration executions will be rejected at submission
  • Scheduled orchestrations will skip their next run and log a warning
  • Event-triggered orchestrations will queue events until the limit resets

Rate Limit Exceeded

When a rate limit is exceeded:

  • The request is queued (not rejected) for a brief period
  • If the queue drains within a reasonable time, the request proceeds
  • If the queue is full or the wait time exceeds a threshold, the request fails with a 429 (Too Many Requests) error
  • DIBOP's built-in retry mechanism respects rate limits and backs off automatically

Storage Quota Exceeded

When storage quotas are exceeded:

  • New data is still written (to avoid data loss)
  • A warning is displayed on the dashboard
  • The platform administrator is notified
  • If the quota remains exceeded for an extended period, the oldest data may be purged early

Configuring Limits

Enterprise Admin

Enterprise Admins can view their current limits but cannot change them. To request a limit increase, contact your platform administrator.

Platform Admin

Platform Admins configure limits per enterprise:

  1. Navigate to Platform Config > Enterprise Management
  2. Select the enterprise
  3. Adjust quotas and rate limits
  4. Save changes

Changes take effect immediately.

Rate Limit Headers

When DIBOP makes API calls to external systems, it respects rate limit headers returned by those systems:

Header Description
X-RateLimit-Limit The maximum number of requests allowed
X-RateLimit-Remaining The number of requests remaining in the current window
X-RateLimit-Reset When the rate limit window resets
Retry-After How many seconds to wait before retrying (on 429 responses)

DIBOP reads these headers and automatically adjusts its request rate to avoid exceeding external system limits. This happens transparently -- you do not need to configure anything.

Optimising Usage

If you are approaching your quotas, consider these strategies:

Reduce Unnecessary API Calls

  • Cache frequently accessed data: If an orchestration calls the same API repeatedly for the same data, consider adding a caching step
  • Batch requests: Some APIs support batch operations (e.g., fetch 100 records in one call instead of 100 individual calls)
  • Filter before calling: Use conditional steps to skip API calls when they are not needed

Optimise Orchestration Frequency

  • Reduce scheduling frequency: If an orchestration runs every minute but hourly is sufficient, reduce the schedule
  • Use event triggers: Instead of polling for changes, use webhooks from external systems to trigger orchestrations when data changes
  • Consolidate orchestrations: If two orchestrations call the same API, consider merging them

Manage Storage

  • Reduce retention periods: Shorter retention means less storage used
  • Export and delete: Export historical data to external storage and reduce DIBOP retention
  • Clean up unused data: Archive orchestrations that are no longer active

Next Steps