Find the symptom, confirm the cause, check, and fix it. If it persists, open a ticket (Support) with the source, the time, and the exact message.
First of all: the connection test#
In ETL/ELT → Connections, use "Test connection" with the source credential and confirm that discovery lists the expected tables. It's the fastest check.
Catalog#
| Symptom | Likely cause | How to check | Fix | Prevention |
|---|---|---|---|---|
| "Test connection" fails right away | invalid/expired credential | review user/token in the connector | update the credential and test again | rotate credentials before they expire |
| OAuth connector stops working after a few days | refresh token not persisted in Bling/Conta Azul/HubSpot | auth error after a while | reconnect the source (new OAuth) | periodic reconnection for now |
| Discovery doesn't list the expected tables | insufficient credential scope/permission | check the scopes granted at the provider | grant the required read scope | document the minimum scopes per source |
| Brazilian ERP/tax system rejects it (Omie/Bling/Tiny/NF-e) | wrong App Key/Secret/token/certificate | validate the credentials in the ERP's panel | fix the credential; for NF-e check the .pfx | store secrets as env vars, never in code |
| Meta Ads / Google Ads won't authorize | App Review / developer token pending | connector in limited access | wait for approval; use within the supported scope | track the status in Connectors |
| Azure Blob doesn't resume where it left off | resumption is by blob name | blob ≤ last processed is skipped | reorder/rename according to the resumption policy | name blobs monotonically |
| Error seems to expose a token | — | it never should: secrets are redacted | if a token appeared in a log/URL, rotate it | treat a leak as a Critical incident |
| "Amazon S3 / pull the customer's GCS bucket" unavailable | the feature is Roadmap (not implemented) | see Status | use an available connector | don't plan a critical integration on Roadmap items |
"Incremental load" is watermark-based, not CDC
Incremental ingestion uses a watermark (a high-water mark per column). True
CDC (change data capture) is Roadmap — see
Incremental ingestion.
Security when reporting#
- Remove secrets from the example before opening a ticket. If a secret leaked in a log/URL, revoke/rotate it first — see Credentials and rotation.
Related#
Last reviewed: 2026-09-08. CDC (change data capture) is planned.