Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-09-08

Troubleshooting: connection and credentials

Symptom → cause → how to check → fix → prevention catalog for connectors, connection testing, and source credentials.

On this page (4)

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.

SymptomLikely causeHow to checkFixPrevention
"Test connection" fails right awayinvalid/expired credentialreview user/token in the connectorupdate the credential and test againrotate credentials before they expire
OAuth connector stops working after a few daysrefresh token not persisted in Bling/Conta Azul/HubSpotauth error after a whilereconnect the source (new OAuth)periodic reconnection for now
Discovery doesn't list the expected tablesinsufficient credential scope/permissioncheck the scopes granted at the providergrant the required read scopedocument the minimum scopes per source
Brazilian ERP/tax system rejects it (Omie/Bling/Tiny/NF-e)wrong App Key/Secret/token/certificatevalidate the credentials in the ERP's panelfix the credential; for NF-e check the .pfxstore secrets as env vars, never in code
Meta Ads / Google Ads won't authorizeApp Review / developer token pendingconnector in limited accesswait for approval; use within the supported scopetrack the status in Connectors
Azure Blob doesn't resume where it left offresumption is by blob nameblob ≤ last processed is skippedreorder/rename according to the resumption policyname blobs monotonically
Error seems to expose a token—it never should: secrets are redactedif a token appeared in a log/URL, rotate ittreat a leak as a Critical incident
"Amazon S3 / pull the customer's GCS bucket" unavailablethe feature is Roadmap (not implemented)see Statususe an available connectordon'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.

Related links