Skip to content

Troubleshooting

These are the messages FACE connectors actually return, grouped by where you see them. An ellipsis (…) stands for a value the message fills in.

Test says “Configuration saved”, with no green tick

Configuration saved — a live connectivity check isn't implemented yet for this source type

This is not a failure. The configuration is stored, and live_check_performed is false because the type has no live probe (SAP). For SAP, use Explore, which reaches the service. See Connections and credentials.

Security refusals

MessageCauseWhat to do
this connection cannot be saved without its security settings: …The connection would send data or a credential unencrypted, skip the certificate check, or lacks a required login. Each problem after the colon names the setting or credential.Set what each problem names. See Security requirements.
this connection is not secured: …; open it in Settings › Integrations and upgrade its securityA stored connection fails the policy, so every read of it is refusedOpen it in Settings › Integrations › Systems and use Upgrade security
nothing was dialled: …Test on a draft that would be refusedFix the settings it names, then Test again
FACE has no security rule for connector type "…", so it cannot be usedThe type has no security ruleUse a supported connector type

Connection and credentials

MessageCauseWhat to do
Unknown connection type "…"The type matches no connector after lowercasing and removing spaces, underscores and hyphensUse a spelling from the connector pages. Google Workspace types (gmail, google_sheets) are read by fetch only.
Connection not foundThe id is no longer stored, for example after a stale listRefresh the list
snowflake connection "…" has no password (or programmatic access token) in its credential store: …The credential bundle has no password, pat or tokenRe-enter the password in the connection form. A password on the record itself is never read.
databricks connection "…" has no personal access token in its credential store: …No personal_access_token in the bundleRe-enter the token
databricks connection "…" names no HTTP path: …http_path is emptyCopy the /sql/1.0/warehouses/… path from the warehouse’s connection details
ssl_mode … can send data unencrypted or ssl_mode is not setdisable, prefer and allow can send data without TLS, and an unset mode cannot be auditedSet require, verify-ca or verify-full
CREDENTIAL_STATE_ABSENT on the listThis node holds no credential bundle for the connectionRe-enter the credential. The state cannot tell “never entered” from “not on this node”.
CREDENTIAL_STATE_UNREADABLE on the listA bundle exists but cannot be openedThis is a key or storage problem on the instance, and re-entering the credential will not fix it. See /docs/operations/.

Fetch

MessageCauseWhat to do
No data source was selected. Choose at least one configured source …The fetch named no connection. FACE reads only the sources you select and never fills in other data.Include at least one connection on Ask (or tick one in the brief), or name one in the request
None of the … selected data source(s) could be processed.Every selected connection was skipped or failed. The message lists each reason after Errors encountered:.Fix the reason given for each connection, for example a missing credential or a connection with no runner

Network

MessageCauseWhat to do
refusing to reach …: it resolves to a … address, which is inside this deployment's own network …The connection is not allowed to reach internal addressesIf the source really is internal, set allow_internal_network=true on the connection
refusing to dial …: that is the cloud instance-metadata service, not a data source. This refusal has no opt-inThe address is the metadata serviceCorrect the address. There is no override.
refusing to dial multicast address … — a data source has one serverMulticast targetUse the source’s unicast address
refusing to follow a redirect from … to …: …The source redirected to a different hostPoint the connection at the final host directly
stopped after 5 redirectsRedirect loopUse the final URL
… returned more than N bytes: refusing to report a partially-read answer as a complete one — …The response exceeded the connector’s capNarrow the request: a shorter window, a smaller page_size, one resource

SQL

MessageCauseWhat to do
only read-only queries (…) are allowedThe statement is not a readSend a read-only statement
query contains restricted keywordsThe statement could change dataRemove the write or DDL clause
this query is a batch of N statements and M bound parameter(s) were supplied: …Parameters were sent with a multi-statement querySend one statement with its parameters
… read N row(s): K of M statement(s) were refused by the engine and their rows are NOT in this result; …Some statements in the batch failed, usually on grantsGrant the role access, or drop those statements

SaaS and ERP

MessageCauseWhat to do
salesforce authentication failed: token endpoint returned 400: …The OAuth username–password flow was rejectedCheck client_id, client_secret, the password plus security_token, and whether the connected app allows this flow
no SOQL to run. …A fetch reached Salesforce with no soql propertySet soql on the connection
`api_version` must look like v60.0; got "…" …Malformed api_versionUse vNN.N
no Guidewire resource to read. …No route configuredSet resource. Explore lists every route the installation declares.
this connection carries a Guidewire username but no password. …The bundle has no passwordRe-enter it
this SAP connection does not say where its OData service is, …No odata_url propertySet odata_url to the service root, or sap_gateway_url to enumerate the Gateway’s catalogue
SAP connector for system … cannot READ rows yet: …A fetch was run against an SAP connection. SAP connections serve metadata.Use Explore for SAP metadata
invalid ServiceNow connection parameters (systemUrl required)Missing systemUrl propertySet it to the instance URL

Files and object storage

MessageCauseWhat to do
missing S3 credentials: provide access_key and secret_keyIncomplete bundleAdd both keys
bucket "…" does not exist at …, or these credentials cannot see itWrong bucket, or no list permissionCheck the name and the policy
reading objects is wired for S3-compatible stores only; …An object read from a GCS or Azure connection. Object reads use S3-compatible stores.Use an S3-compatible endpoint for object reads
no object key given: pass the key to read as the queryExecute was called without a keyPass the object key as the query
"…" is not an .xlsx/.xlsm file — use the CSV format for delimited textExcel connection pointed at another formatUse an object-store connection for CSV

Streaming and telemetry

MessageCauseWhat to do
kafka extraction …A fetch was run against a Kafka connection. Kafka connections serve the topic catalogue.Use Explore for the topic catalogue
no bootstrap server answered: …No broker completed the handshakeCheck addresses, security_protocol and SASL settings
sasl_mechanism "…" is not allowed: set it to scram-sha-512 or scram-sha-256Only SCRAM is acceptedUse scram-sha-512 or scram-sha-256 over sasl_ssl, on a listener that offers it
SCRAM server signature does not verify: …The broker accepted the proof but could not prove it holds the credentialThe peer is not the broker the credential was created on: check bootstrap_servers and the listener
TLS handshake with broker … failed: x509: certificate signed by unknown authorityThe broker’s certificate is from a private CAPaste that CA’s certificate into ssl_ca_pem
no topics configured for broker …: …The MQTT topics list is emptyList the topic filters to read. FACE never defaults to #.
broker_url has no TLS scheme: … or broker_url uses …://, which is unencryptedThe MQTT broker address is not TLSUse the broker’s tls://, ssl://, mqtts:// or wss:// listener, with use_tls on
qos 2 is configured but …: set qos to 0 or 1QoS 2 is configured. The connector delivers at QoS 0 and 1.Use QoS 0 or 1
<type> connector reached … and received no readingsConnected, but nothing arrived in the windowCheck that devices are publishing, and lengthen collect_seconds
rfid: no endpoint configured: …Reader address missingSet endpoint
gps connection has no provider: expected one of samsara, geotab, generic_rest, nmeaNo provider set on a non-URL endpointSet provider to samsara, geotab or generic_rest. nmea is refused (next row).
provider nmea is a raw TCP stream with no encryption, so FACE cannot secure it: …An NMEA connectionUse the tracker’s https API (generic_rest) instead
sensor gateway transport is "mqtt", which this connector does not serve: …MQTT configured on a gateway connectionCreate an mqtt connection instead
gateway at … accepted the connection but reading channel "…" (asset …, register … on unit …) failed: …Wrong register, unit id or register typeCheck the channel’s address, register_type and unit_id against the gateway’s register map
… connection is configured for API-key auth but no key is stored: …Logistics API with no api_key credentialAdd the key, or change auth_mode

Cameras and edge

MessageCauseWhat to do
cannot reach RTSP feed at …: …The camera did not accept a TCP connectionCheck the host, the rtsps:// port and the network path
feed rejected the credentials (HTTP 401)Wrong camera credentialsRe-enter the username and password
device_capture is set but endpoint_url is also "…": choose one — …Both push and pull are configuredClear one of them
unsupported image format "…" (only jpeg/png accepted)A pushed frame is not JPEG or PNGSend JPEG or PNG
the Flipper agent at … is running but has no device: …The agent is up with no Flipper attachedConnect and power on the device