Getting started Community Training Tutorials Documentation APIs, AI & Tools
<AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG"/>
To troubleshoot Spiff Connector, become familiar with the information about enabling verbose logging and interpreting common errors.
The connector doesn’t log requests and responses itself. The Mule HTTP service does. To log each Spiff request and
response, add this logger to the app’s log4j2.xml:
<AsyncLogger name="org.mule.service.http.impl.service.HttpMessageLogger" level="DEBUG"/>
The HTTP service logs the headers and bodies as sent, including the signature header. The webhook secret is never
sent, so it is never logged. Record bodies can contain personal data, so enable this logger only while you troubleshoot.
The connector logs its own decisions at DEBUG under com.mulesoft.connectors.spiff, for example an ignored
connector-managed header, an ignored company_uuid query parameter, or an error response body that couldn’t be read:
<AsyncLogger name="com.mulesoft.connectors.spiff" level="DEBUG"/>
To check which cryptographic provider the connector uses, for example on a FIPS 140 runtime, enable DEBUG for this logger:
<AsyncLogger name="com.mulesoft.connectors.spiff.internal.connection.SpiffSignatureGenerator" level="DEBUG"/>
SpiffSignatureGenerator logs the JCA provider of HmacSHA256, for example the Bouncy Castle FIPS provider on a FIPS 140 runtime.
The connector runs the input checks and starts each request on a Mule I/O scheduler named
spiff.<configuration name>.operations. Look for that name in thread dumps.
Use this table to interpret errors that occur when you test the Spiff connection in Studio.
| Error | Description |
|---|---|
|
Copy the current webhook secret from Spiff Admin. If it was refreshed, update the secure property. |
|
The webhook secret belongs to a different connector. |
|
The Connector ID or Company UUID is wrong, or the Subdomain points at a different environment. |
|
The Connector ID is the base64 ID instead of the raw integer. |
|
Check DNS, firewall, proxy, TLS settings, and the Subdomain value. |
|
The Connector ID contains non-digit characters or is out of range. |
|
The Company UUID isn’t in |
|
The Webhook Secret field is empty. |
|
Spiff answered with a status other than 200, including another 2xx status. Only HTTP 200 passes Test Connection. Check that Subdomain points at a Spiff host. |
Here is a list of commonly thrown exception messages and how to interpret them:
SPIFF:UNAUTHORIZED
The webhook secret is wrong or was refreshed in Spiff Admin. Update the secure property and redeploy. If the error occurs only on some hosts, verify that every host uses the same secret and that each host clock is synchronized with NTP.
MULE:CONNECTIVITY
Test Connection raises this error when the Connector ID isn't digits only, for example when it is the base64 Relay ID, or when it is larger than the largest 64-bit integer. Use the raw integer from *Spiff Admin* > *Connectors*. The connector rejects it before sending any request.
SPIFF:NOT_FOUND
Verify that the Connector ID, Company UUID, and Mapping ID belong to the same Spiff tenant, and that Subdomain points at that tenant's environment (`us1` versus `eu1` versus a Salesforce-hosted URL). Deleting a record that doesn't exist succeeds, so this error indicates an unknown Mapping ID or Connector ID, not a missing record.
SPIFF:PAYLOAD_TOO_LARGE
Reduce the batch size. The limit is 5 MiB (5,242,880 bytes) of JSON per request. The connector rejects a larger body before it sends the request; Spiff can also answer HTTP 413.
SPIFF:UNPROCESSABLE_ENTITY
Spiff answered HTTP 422 because it rejected the record values. Check the expected fields in the record operation's DataSense input type for the Mapping ID, or in *Spiff Admin* > *Synced Objects & Fields*.
SPIFF:INVALID_INPUT
An array element must be a non-empty JSON object, the Mapping ID must be the integer ID of a Spiff mapping, and the payload must be valid JSON. Filter out empty records, select the Mapping ID from the dropdown or use the integer ID from Spiff Admin, and use `output application/json` in the DataWeave expression that builds the body.
SPIFF:CLIENT_ERROR
A 3xx status indicates that Subdomain points at a host that redirects. The error message names the redirect `Location`; use that final Spiff host. The connector doesn't follow redirects, so a signed request is never re-sent to another host.
| Symptom | Resolution |
|---|---|
An operation succeeds but the record doesn’t appear in Spiff |
Spiff validates record bodies asynchronously. A success response only means that Spiff accepted the signature and the IDs, not that the record was written. For example, a record without its identity field (usually |
No input metadata when the Mapping ID is an expression |
DataSense needs a fixed Mapping ID value. With an expression such as |
No mappings in the Mapping ID dropdown |
Test Connection first. A connector without mappings returns an empty list. Configure mappings in Spiff Admin > Synced Objects & Fields. |
The Mapping ID dropdown shows mappings but the input metadata has no fields |
The mapping has no translator fields yet. Configure them in Spiff Admin, then refresh metadata. |