Provider rate limits often apply to a whole account, even when several credentials and workers use it. Configure Domain Nexus's shared request budget so those connections coordinate within the installation. A provider's advertised quota, the module's local pacing and your chosen operating budget are related but different values.
IN THIS ARTICLE
01 Set a shared account scope
- Inventory all Domain Nexus connections that use the same provider account or project and therefore share a quota.
- Open each applicable server connection's advanced options.
- Set the same Shared provider account identifier for those connections. Use a stable non-secret account label. Never paste an API key or password into this field.
- Set Shared requests per window and Shared window in seconds using the provider's verified account-specific allowance and a practical margin for other applications.
- Save all related connections and review background jobs during a controlled operation before launching a large import or replication run.
02 Understand the boundary
The shared budget coordinates web and workers that use this module database. It cannot count an unrelated installation, a third-party DNS script or a human changing records in the provider's panel. Reserve capacity for those callers, or coordinate their schedules separately.
The adapter also applies its own request pacing and handles provider retry instructions. The default self-imposed budget is not a statement that the vendor permits the same number of requests for every plan, endpoint or account. A provider may have additional per-zone or daily restrictions.
Why did a job defer instead of finish immediately?
Deferral can preserve the provider's quota while durable work remains pending. Inspect the task's status and retry timing rather than creating duplicate bulk jobs. If delays persist, compare the actual workload with the configured shared account scope and the provider's response.
What changes during key rotation?
Keep the stable shared account identifier when replacing a credential for the same quota pool. Otherwise separate keys may appear to be unrelated callers. If the replacement belongs to a genuinely different provider account, assign its own scope and recheck zone ownership before using it.