Low Code & No Code
Partner with us 💰Try Foxentry 🦊

Troubleshooting & QNA 💡

Error 401: Unauthorized

Symptom: You start the validation process, but it immediately fails or the logs show a series of 401 Unauthorized HTTP responses.

Cause: The application cannot authenticate with the Foxentry API. This is usually caused by:

  1. An incorrect or empty API key.
  2. The API key has been deleted or has passed its expiration date.
  3. IP Restrictions: The key is restricted to specific IP addresses in the Foxentry dashboard, and your current local IP does not match the whitelist.

Solution:
Log into your Foxentry dashboard, navigate to your API project settings, and verify the status of your key. Ensure that your current public IP address is authorized. When in doubt, generate a new key and paste it into the Data Cleaner.

Missing Columns in Output (Data Not Validated)

Symptom: The validation finishes successfully and the output file is generated, but the expected _result and _updated columns are missing, or specific fields seem completely untouched.

Cause: This is almost always a mapping issue during Step 2 (Columns).

  • The columns were left mapped as — ignore —.
  • Data Groups were misconfigured (e.g., mapping a City to Address 1 but the ZIP code to Address 2, breaking the validation logic).
  • The First row is header checkbox was checked, but your file didn't have headers, causing the first row of actual data to be skipped.

Solution:
Rerun the application, double-check your column mapping, and ensure that all related fields for a single record are assigned to the exact same group index (e.g., all parts of a billing address must be grouped under Address 1).

Apostrophes Added to Data (CSV Injection Protection)

Symptom: You open your cleaned file in Microsoft Excel or Google Sheets, and you notice that some corrected values or suggestions start with a single quote/apostrophe (e.g., '=123 Main St).

Cause: This is an intentional security feature. Spreadsheet applications will automatically execute any cell content that begins with mathematical or command characters (such as =, +, -, or @) as a formula. If malicious data is injected this way, it can compromise your machine (known as CSV Injection or Formula Injection). To prevent this, Foxentry Data Cleaner automatically escapes these vulnerable characters by prepending an apostrophe.

Solution:
This behavior is highly recommended for security. However, if you are absolutely certain your data is safe and you need to disable this escaping for strict database imports, you can turn off CSV Injection Protection in the advanced settings (the gear icon ⚙️) on the first screen.

Status Values & Unrecognized Errors

If you encounter other HTTP errors (such as 400 Bad Request or 422 Unprocessable Entity), it generally means the mapped combination of data is unsupported or violates the endpoint's prerequisites.

To understand specific status codes and error messages, we highly recommend enabling Request Logs (on the Step 4 Order page) to view the raw JSON responses. You can then cross-reference the errors with our main API documentation: