Connector States
There are four types of "state" a connector or flow can be in. These states may have slightly different meanings depending on if it's associated with a source, destination, or flow.
State Definitions
 | Inactive | Shown when the source or flow is marked inactive. Mark the source of flow "active" to clear this state. No data processing will occur when inactive. |
 | Active / Healthy | Shown when everything is nominal with the source, destination, or flow. |
 | Provisioning / Idle | Source, destination, or flow is not processing data. See below for details. |
 | Error | Source, destination, or flow has errors. See below for details. |
Hovering over a state icon will reveal additional state information
If a source, destination, or flow is in an Error state, detailed error messages can be seen under the "Errors" tab on the source, destination, or flow "Details" page.
Sources
| Provisioning | A source is configured, but has not started ingesting data. |
| Idle | A source is configured, but not part of any flows, or only part of inactive flows. |
| Idle | The source is not pulling in any data from a healthy connection. e.g. 0 records returned. |
| Idle | If a source connection fails, but on the next test succeeds, the source we will be in an idle state until that source ingests data again. |
| Error | This source has errors with it's configuration or API requests. |
Destinations
| Provisioning | A destination is configured, but has not yet received it's first batch of data via a configured flow. |
| Idle | A destination is configured, but not processing any data. |
| Error | The destination has errors with it's configuration or authentication. |
Flows
| Provisioning | A flow is configured, but has not yet processed it's first batch of data. |
| Idle | A flow is configured, but the source connector is inactive. |
| Error | Errors encountered when processing data. e.g. an invalid JSON record is present |
Updated 6 days ago