procore-rate-limits
/procore-rate-limits
Implement adaptive Procore throttling from response headers across spike, hourly, and heavy-load conditions. Use when handling 429 or 503 responses, sizing concurrency, or protecting webhook backlogs. Trigger with: "handle Procore rate limits", "fix Procore 429", "throttle Procore workers".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement adaptive Procore throttling from response headers across spike, hourly, and heavy-load conditions. Use when handling 429 or 503 responses, sizing concurrency, or protecting webhook backlogs. Trigger with: "handle Procore rate limits", "fix Procore 429", "throttle Procore workers".
Triggers from the description
Arguments
/procore-rate-limits [worker-and-request-class]
Original author description
Implement adaptive Procore throttling from response headers across spike, hourly, and heavy-load conditions. Use when handling 429 or 503 responses, sizing concurrency, or protecting webhook backlogs. Trigger with: "handle Procore rate limits", "fix Procore 429", "throttle Procore workers".
How it works
- Overview
- Prerequisites
- Instructions
- Authentication
- Tool Discipline
- Output
- Examples
- Error Handling
- Resources
SKILL.md preview
--- name: procore-rate-limits description: >- Implement adaptive Procore throttling from response headers across spike, hourly, and heavy-load conditions. Use when handling 429 or 503 responses, sizing concurrency, or protecting webhook backlogs. Trigger with: "handle Procore rate limits", "fix Procore 429", "throttle Procore workers". allowed-tools: Read, Grep, Write, Edit version: 2.0.0 argument-hint: '[worker-and-request-class]' model: inherit effort: high license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: - saas - procore - rate-limits - resilience compatibility: 'Requires access to Procore response headers and a queue or scheduler capable of pausing and bounding concurrency.' --- # Procore Header-Driven Rate Controller ## Overview Control throughput from the headers on each response instead of a hard-coded request count. Procore exposes whichever spike or hourly window is most likely to bind, and failed requests consume the same budget as successful calls. ## Prerequisites - Central request dispatcher with observable worker concurrency - Durable queue and a clock synchronized well enough to interpret reset timestamps - Metrics for status, route, remaining budget, reset time, retries, and backlog age ## Instructions ### Step 1: Capture every budget signal Record `X-Rate-Limit-Limit`, `X-Rate-Limit-Remaining`, and `X-Rate-Limit-Reset` from each response. Preserve `Retry-After` for heavy-load responses. ### Step 2: Pace before exhaustion Reduce dispatch concurrency as remaining budget falls and pause when it reaches zero. Treat the current headers as authoritative for either the spike or hourly window. ### Step 3: Handle throttling On 429, wait until after the reported reset and add jitter before resuming. On 503, obey `Retry-After`; never substitute an assumed delay. ### Step 4: Bound retries Retry safe reads within a capped policy. For writes, reconcile outcome or require an operation-specific idempotency design before another attempt. ### Step 5: Protect event backlogs Acknowledge webhook notifications quickly, enqueue downstream reads, and let the controller drain them. Monitor oldest-event age as well as queue depth. ### Step 6: Prove recovery Test low-budget, exhausted-budget, 429, and 503 fixtures. Verify one worker cannot bypass the shared controller and that recovery does not release a synchronized surge. ## Authentication Requests retain their existing OAuth 2.0 Bearer token and company routing. Throttling must not acquire alternate credentials to evade a rate boundary or log tokens alongside rate metadata. ## Tool Discipline Use Read and Grep to inspect dispatcher code, metrics, and provider headers. Use Write or Edit only for the approved limiter, queue policy, tests, or receipt; do not generate live load as a rate-limit test. ## Output - Header-driven pacing and retry policy - Deterministic limit and recovery tests - Route-level budget, backlog, and failure metrics Return the observed headers, controller decision, retry eligibility, next dispatch time, and verification outcome. ## Examples When remaining budget reaches zero, all workers stop until the reported reset plus jitter. A 503 follows its Retry-After value, while an ambiguous write is reconciled rather than replayed with the safe-read policy. ## Error Handling | Failure | Response | | --- | --- | | Rate headers missing | Reduce concurrency conservatively and surface telemetry loss; do not invent a limit. | | 429 repeats after reset | Increase jitter, lower concurrency, and inspect failed-call volume. | | Queue age breaches objective | Shed optional work and prioritize reconciliation without bypassing the limit. | | Write retry safety is unknown | Stop automatic retries and reconcile provider state. | ## Resources - [First-party source notes](references/official-docs.md) - [Rate limiting](https://developers.procore.com/documentation/rate-limiting) - [API Call Activity Report](https://developers.procore.com/documentation/api-activity-export) - [Error code reference](https://developers.procore.com/documentation/error-reference)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named procore-rate-limits.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 05f04846d00b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100procore-common-errors
Triage Procore OAuth, routing, permission, validation, pagination, throttling, and webhook failures without widening access or retrying blindly. Use when a Procore integration returns 4xx or 5xx responses, empty data, or missing deliveries. Trigger with: "debug Procore 403",… - 100procore-sdk-patterns
Design a thin Procore REST client that preserves endpoint-specific versions, company routing, pagination links, errors, and rate headers. Use when building or reviewing a shared HTTP adapter instead of copying ad hoc requests. Trigger with: "build a Procore client", "review… - 100procore-webhooks
Receive and authenticate Procore construction webhooks. Use when setting up a Procore company or project webhook (hook) endpoint, checking the Authorization Header credential, debugging 401s, or handling resource create, update and delete events such as RFIs or submittals. - 100deepgram-rate-limits
Implement Deepgram rate limiting and backoff strategies. Use when handling API quotas, implementing request throttling, or dealing with rate limit errors. Trigger with phrases like "deepgram rate limit", "deepgram throttling", "429 error deepgram", "deepgram quota", "deepgram backoff". - 100apollo-rate-limits
Implement Apollo.io rate limiting and backoff. Use when handling rate limits, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "apollo rate limit", "apollo 429", "apollo throttling", "apollo backoff", "apollo request limits".