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 type has no live probe (SAP, Dynamics 365, HubSpot,
SharePoint), so live_check_performed is false and nothing was verified. For SAP,
use Explore, which does reach the service. See
Connections and credentials.
Connection and credentials
| Message | Cause | What to do |
|---|---|---|
Unknown connection type "…" | The type matches no connector after lowercasing and removing spaces, underscores and hyphens | Use a spelling from the connector pages. Google Workspace types (gmail, google_sheets, google_docs) are read by fetch only. |
Connection not found | The id is no longer stored, for example after a stale list | Refresh the list |
snowflake connection "…" has no password (or programmatic access token) in its credential store: … | The credential bundle has no password, pat or token | Re-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 bundle | Re-enter the token |
databricks connection "…" names no HTTP path: … | http_path is empty | Copy the /sql/1.0/warehouses/… path from the warehouse’s connection details |
ssl_mode "prefer" is not accepted: … (also "allow") | These modes can fall back to cleartext | Use require (the default), verify-ca, verify-full, or disable on purpose |
CREDENTIAL_STATE_ABSENT on the list | This node holds no credential bundle for the connection | Re-enter the credential. The state cannot tell “never entered” from “not on this node”. |
CREDENTIAL_STATE_UNREADABLE on the list | A bundle exists but cannot be opened | This is a key or storage problem on the instance, and re-entering the credential will not fix it. See /docs/operations/. |
Network
| Message | Cause | What to do |
|---|---|---|
refusing to reach …: it resolves to a … address, which is inside this deployment's own network … | The connector refuses internal addresses by default | If 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-in | The address is the metadata service, directly or through NAT64 | Correct the address. There is no override. |
refusing to dial multicast address … — a data source has one server | Multicast target | Use the source’s unicast address |
refusing to follow a redirect from … to …: … | The source redirected to a different host | Point the connection at the final host directly |
stopped after 5 redirects | Redirect loop | Use 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 cap | Narrow the request: a shorter window, a smaller page_size, one resource |
SQL
| Message | Cause | What to do |
|---|---|---|
only read-only queries (SELECT, WITH, SHOW, DESCRIBE, EXPLAIN) are allowed | The statement is not a read | Send a read-only statement |
query contains restricted keywords | The statement contains a blocked keyword | Remove 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 query | Send 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 grants | Grant the role access, or drop those statements |
BigQuery queries are not executable yet: … | BigQuery execution is not available | — |
SaaS and ERP
| Message | Cause | What to do |
|---|---|---|
salesforce authentication failed: token endpoint returned 400: … | The OAuth username–password flow was rejected | Check 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 property | Set soql on the connection |
`api_version` must look like v60.0; got "…" … | Malformed api_version | Use vNN.N |
no Guidewire resource to read. … | No route configured | Set resource. Explore lists every route the installation declares. |
this connection carries a Guidewire username but no password. … | The bundle has no password | Re-enter it |
this SAP connection does not say where its OData service is, … | No odata_url property | Set odata_url to the service root, or sap_gateway_url to enumerate the Gateway’s catalogue |
SAP connector for system … cannot READ rows yet: … | SAP row extraction is not built | Use Explore for SAP metadata |
invalid ServiceNow connection parameters (systemUrl required) | Missing systemUrl property | Set it to the instance URL |
Files and object storage
| Message | Cause | What to do |
|---|---|---|
missing S3 credentials: provide access_key and secret_key | Incomplete bundle | Add both keys |
bucket "…" does not exist at …, or these credentials cannot see it | Wrong bucket, or no list permission | Check the name and the policy |
reading objects is wired for S3-compatible stores only; "…" is not yet supported | Reading GCS or Azure objects | Use an S3-compatible endpoint for object reads |
no object key given: pass the key to read as the query | Execute was called without a key | Pass the object key as the query |
"…" is not an .xlsx/.xlsm file — use the CSV format for delimited text | Excel connection pointed at another format | Use an object-store connection for CSV |
Streaming and telemetry
| Message | Cause | What to do |
|---|---|---|
kafka extraction is not implemented: … | Kafka records cannot be read yet | Use Explore for the topic catalogue |
no bootstrap server answered: … | No broker completed the handshake | Check addresses, security_protocol and SASL settings |
sasl_mechanism SCRAM-SHA-256 is configured but only PLAIN is implemented here: … | Unsupported SASL mechanism | Use PLAIN over sasl_ssl, or a listener that offers it |
no topics configured for broker …: … | The MQTT topics list is empty | List the topic filters to read. FACE never defaults to #. |
broker URL "…" uses the ws scheme: MQTT over WebSocket is not implemented — … | WebSocket broker URL | Use the broker’s tcp:// or tls:// listener |
qos 2 is configured but the QoS 2 delivery handshake (PUBREC/PUBREL/PUBCOMP) is not implemented: set qos to 0 or 1 | QoS 2 | Use QoS 0 or 1 |
<type> connector reached … and received no readings | Connected, but nothing arrived in the window | Check that devices are publishing, and lengthen collect_seconds |
rfid: no endpoint configured: … | Reader address missing | Set endpoint |
gps connection has no provider: expected one of samsara, geotab, generic_rest, nmea | No provider set on a non-URL endpoint | Set provider |
sensor gateway transport is "mqtt", which this connector does not serve: … | MQTT configured on a gateway connection | Create an mqtt connection instead |
gateway at … accepted the connection but reading channel "…" (asset …, register … on unit …) failed: … | Wrong register, unit id or register type | Check 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 credential | Add the key, or change auth_mode |
Cameras and edge
| Message | Cause | What to do |
|---|---|---|
cannot reach RTSP feed at …: … | The camera did not accept a TCP connection | Check the host, the port (554 by default) and the network path |
feed rejected the credentials (HTTP 401) | Wrong camera credentials | Re-enter the username and password |
device_capture is set but endpoint_url is also "…": choose one — … | Both push and pull are configured | Clear one of them |
unsupported image format "…" (only jpeg/png accepted) | A pushed frame is not JPEG or PNG | Send JPEG or PNG |
the Flipper agent at … is running but has no device: … | The agent is up with no Flipper attached | Connect and power on the device |