Operating Your Extension
Marketplace publication starts an operational commitment: monitor the integration, support installations, and release compatible upgrades.
Responsibility boundary
Throttle operates
- Catalog, versions, installations, and review systems
- Scoped extension credentials and identity tokens
- Signed event delivery and delivery logs
- Marketplace availability and platform status
The publisher operates
- Application hosting, queues, and persistence
- Third-party credentials and provider API use
- Mapping, reconciliation, monitoring, and alerting
- Customer support, privacy obligations, and incident response
Baseline telemetry
Record the Throttle request ID, installation ID, event ID and type, extension version, provider account reference, attempt number, duration, result class, and environment. Use structured logs so one installation can be traced without searching payload contents.
Never log secrets
Do not log API keys, webhook signing secrets, access tokens, authorization headers, or customer-sensitive request bodies. Redact provider responses before attaching them to support cases.
Incident and lifecycle procedures
- Back off and reconcile after provider outages or rate limiting.
- Surface expired credentials as an actionable installation state.
- Quarantine poison events and provide a replay procedure.
- Pause new installs or move the listing private during a material incident.
- Keep upgrades backward compatible; document and review new scopes.
- Publish deprecation notice and data export/deletion instructions before retirement.
- On uninstall, revoke provider access and stop scheduled or queued work safely.
Use the Versioning guide for releases and the marketplace guide for listing changes or re-review.