---
title: "The connector doctor ran on an installation and found something different from the previous run."
method: POST
path: "connector.doctor_completed"
tags: ["connector.* events"]
---

# The connector doctor ran on an installation and found something different from the previous run.

`POST connector.doctor_completed` (webhook)

### When this fires

The creator pressed **Run Doctor** on the Connectors tab or the connector's page, an integration called [the doctor endpoint](https://docs.subscriby.net/api/v1/reference/connectors) or [`run_connector_doctor`](https://docs.subscriby.net/mcp/v1/tools/connectors/run-connector-doctor), or the platform's scheduled sweep ran, and the report differs from the one kept on the installation: a finding appeared, disappeared or changed severity or state. A run that finds exactly what the last one found fires nothing, so a nightly sweep is quiet until something moves. The installation's own verification inside the run still fires `connector.status_changed` when the state moved.

### Caveats

- The first run on an installation fires this event, because there is no earlier report to match; a repeat with the same findings does not.
- A resource the connector has no place it can ask about (no space row, no legacy chat) is a `warning` finding, never left out.
- Sentences are rendered in the creator's language at the time of the run; the `state` words are stable.

### Related events

- `connector.status_changed`: the installation's own verdict, fired by the verification inside the run when the state moved.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'connector.doctor_completed', required: The event name, always `connector.doctor_completed` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `connector` string, required: The connector key.
    - `installation_id` string, uuid, required: The installation examined.
    - `project_id` string, uuid, required: The project, repeated inside the payload.
    - `ran_at` string, date-time, required: When the doctor ran.
    - `healthy` boolean, required: Whether every finding is `ok`.
    - `critical` integer, required: Findings the connector can no longer act on.
    - `warnings` integer, required: Findings the connector could not confirm.
    - `findings` object[], required: Every check, the installation first, then one per gated resource.
      - `key` string, required: `installation`, or `resource:<resource id>`.
      - `kind` 'installation' | 'resource', required: What was checked.
      - `severity` 'ok' | 'warning' | 'critical', required: How the finding stands.
      - `subject` string, required: What was checked, as the creator names it.
      - `state` string, required: The connector's word for how it stands: an installation state, or a space access state.
      - `message` string, required: One sentence in the creator's language.
      - `creator_actionable` boolean, required: Whether the creator can fix it themselves.
      - `fix_url` string, uri, nullable, required: Where they go to fix it, when there is a page.
      - `resource_id` string, uuid, nullable, required: The resource, for a resource finding.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)