Check connectors and connections
Open integrations, check connection status and narrow down errors safely
Connectors link SimpliServ with external services. The status only shows whether the technical connection works; it doesn't automatically confirm that data was synchronised correctly in business terms.
Before testing
- Which connector is affected?
- Which direction is affected: import, export or both?
- Since when does the error occur?
- Is there a specific external ID or record you can check against?
- Has a token, password, webhook or permission changed?
Check the connection
Open the connector
Open Administration → Data & devices → Connectors. Active connections are listed under Active with the status Connected; Active only hides all others. Open the affected connector via Manage. Don't change several connections at once.
Read status and last run
Depending on the connector, the Overview tab shows figures such as Last sync, Last used, Token expires and a status (Healthy, Pending, Failed or Not configured). Credentials and options are in the Configuration tab.
Test without changing business data
Use the existing test or connection check first. Don't start a full import if only authentication is unclear.
Compare one record
Look up an external ID and compare name, status, price, tax and timestamps in both systems. Note differences before synchronising again.
Common causes
| Symptom | Likely cause | Next check |
|---|---|---|
| Connection expired | token or OAuth consent expired | disconnect the connector and Connect again |
| Test green, data missing | filter, mapping or missing trigger | check last run and filter |
| Duplicate records | repeated import without a stable external ID | check import rules and idempotency |
| Only some fields wrong | mapping or custom field changed | compare a sample record |
Never store credentials in tickets, screenshots or free text. After an authorisation change, check a single test record first.
After an error
Export or copy the technical error message, note connector, time and external ID and link the entry in the admin log. Repeated full imports without root-cause analysis can create duplicates and overwrites.
How is this guide?