salesforce-reliability-patterns
/salesforce-reliability-patterns
Buduje niezawodność integracji Salesforce: idempotencja, ograniczone ponowienia, trwały stan, dead letters, uzgodnienia, backfill i przetestowane odtwarzanie po awarii.
- Autor
- jeremylongshore ↗
- Repozytorium
- tons-of-skills-marketplace ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Buduje niezawodność integracji Salesforce: idempotencja, ograniczone ponowienia, trwały stan, dead letters, uzgodnienia, backfill i przetestowane odtwarzanie po awarii.
Wyzwalacze z opisu
Argumenty
/salesforce-reliability-patterns [integration] [failure-mode]
Oryginalny opis (EN)
Build Salesforce integration reliability with idempotency, bounded retries, durable state, dead letters, reconciliation, backfill, and tested recovery. Use when designing resilient systems. Trigger with "harden Salesforce reliability".
Jak działa
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Example
Podgląd SKILL.md
--- name: salesforce-reliability-patterns description: 'Build Salesforce integration reliability with idempotency, bounded retries, durable state, dead letters, reconciliation, backfill, and tested recovery. Use when designing resilient systems. Trigger with "harden Salesforce reliability".' argument-hint: "[integration] [failure-mode]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.8.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: [saas, salesforce, reliability, idempotency, recovery] model: inherit effort: high compatibility: Designed for Claude Code; retry, replay, queue, failover, and data repair changes require system and data-owner approval --- # Salesforce Reliability and Recovery Patterns ## Overview Make every read, write, job, and event path safe under duplicate, delayed, partial, uncertain, throttled, and unavailable outcomes. ## Prerequisites - Business invariants, sources of truth, operation classes, stable keys, ordering, latency, and recovery objectives - Current Salesforce API, event, limit, error, job-result, and transaction contracts - Durable queue and checkpoint stores, quarantine or dead-letter path, reconciliation, backfill, and owners ## Tool Discipline Use `Read`, `Glob`, and `Grep` to inspect approved repository and evidence files, `WebFetch` to re-check current first-party Salesforce documentation, and `Write` or `Edit` only for secretless plans, fixtures, configuration, and redacted receipts. ## Current Contract Salesforce synchronous, composite, bulk, and event surfaces have different transaction, result, retry, ordering, and recovery semantics. CDC can emit gap or overflow events; no transport removes the need for idempotency and reconciliation. ## Authentication Use separate minimum-permission principals for runtime, repair, and diagnostics. Protect tokens, payloads, checkpoints, dead letters, and repair tooling from unauthorized access and logging. ## Instructions 1. Classify each operation as read, create, update, upsert, delete, job, publish, or consume and define its invariant and stable key. 2. Document timeout, error, partial-result, transaction, limit, ordering, duplicate, replay, and retention semantics from current contracts. 3. Design idempotency through external IDs, request ledgers, deduplication keys, conditional state, or invariant checks appropriate to the operation. 4. Retry only classified transient failures with bounded attempts, jitter, budget, and circuit breaking; reconcile uncertain outcomes first. 5. Persist queue, job, checkpoint, schema, and dead-letter state durably with redaction, retention, and ownership. 6. Test token expiry, timeouts, partial writes, locks, hard limits, duplicate events, gaps, schema drift, consumer outage, and restart. 7. Run recovery and backfill drills, compare against the source of truth, and measure recovery objectives and duplicate business effects. ## Approval Boundaries Do not replay, purge queues, skip failed records, alter checkpoints, repair data, fail over, or change retry budgets without application and data owners. ## Output Return the operation contracts, failure matrix, idempotency and retry design, durable-state schema, test results, recovery receipt, gaps, and owners. ## Error Handling | Condition | Response | |---|---| | Write timed out with unknown outcome | Reconcile by stable key or request ledger before any retry. | | Event gap or overflow is detected | Bound the interval and use the approved source-of-truth reconciliation or backfill. | | Dead-letter payload contains sensitive data | Restrict and redact the store, assess exposure, and repair producers before replay. | ## Example A redacted completion receipt might look like this: ```text integration=orders; key=erp_id; retries=transient-only; ledger=durable; dlq=encrypted; chaos=pass; recovery=42m ``` ## Resources - [Change Data Capture](https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_intro.htm) - [Composite REST resources](https://developer.salesforce.com/docs/platform/api-rest/guide/resources-composite-composite.html) ## Next Steps Run the workflow first in the lowest-risk authorized org and preserve its redacted receipt. Schedule a review against the next Salesforce seasonal release and the customer change calendar.
Wersje
W bazie nie ma innych skilli o nazwie salesforce-reliability-patterns.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki fef786c35885 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100firecrawl-reliability-patterns
Wdraża ograniczone ponowienia, trwały stan asynchroniczny, paginację, idempotencję, uzgadnianie, wyłączniki, anulowanie i tryby degradacji dla Firecrawl v2 w integracji produkcyjnej. - 100exa-reliability-patterns
Projektuje ograniczone ponowienia, terminy, zachowanie przy częściowych wynikach i przetestowane fallbacki Exa według endpointu i klasy awarii. - 90salesforce-architecture
Pomaga w architekturze organizacji Salesforce: planowanie pojemności, przegląd bezpieczeństwa i udostępniania, wzorce integracji i dług techniczny. - 100specialized-salesforce-architect
Projektuje architekturę rozwiązań Salesforce: układ wielu chmur, wzorce integracji, limity platformy, wdrożenia i model danych. - 100salesforce-integration-review-skill
Przegląda projekt integracji Salesforce pod kątem wyboru API, pozycji middleware, ponowień i idempotencji, kolejek błędów, obserwowalności, sekretów, zakresów OAuth i wzorców MuleSoft. - 90background-jobs
Projektuje zadania kolejkowane i harmonogramowe odporne na duplikaty, ponowienia, awarie i restarty: kontrakt zadania, idempotencja, backoff, dead letters i gwarancje kolejności.