This guide covers the most common issues TexAu users run into, with step-by-step solutions for each. If your issue is not listed here, contact our support team with the details described in the "Still stuck?" section at the bottom.
Import failures
"File is too large to import"
What this means: Your file exceeds the 10 MB upload limit.
How to fix it:
- Check your file size. Right-click the file and view its properties. If it exceeds 10 MB, you need to split it.
- Split your data into smaller files. Open the file in a spreadsheet application, divide it into chunks of 5-8 MB each, save each as a separate CSV, and import them one at a time.
- Reduce file bloat. Remove columns you do not need enriched, delete blank rows, and remove duplicate entries before importing.
- Re-save as CSV. If you exported from a spreadsheet application, confirm you saved as "CSV (Comma-delimited)" and not another format.
This table scrolls sideways on small screens.
| File Size | Recommended Action |
|---|---|
| Under 10 MB | Import directly |
| 10-50 MB | Split into 2-5 files |
| 50-100 MB | Split into 5-10 files, remove unnecessary columns |
| Over 100 MB | Remove unused columns first, then split |
"Too many columns detected"
What this means: Your file contains more than 100 columns. TexAu supports up to 100 columns per table.
How to fix it:
- Keep only the columns you need. Remove any columns that are not relevant to your enrichment or analysis goals.
- Split columns across multiple imports. If you genuinely need more than 100 columns, create separate tables for different data categories and link them by a shared identifier (such as email or company domain).
- Contact support. If you have a legitimate use case requiring more than 100 columns, let us know and we can discuss options.
"Unrecognized file format"
What this means: The file you uploaded is not in a format TexAu can process.
Common causes:
- File is in spreadsheet format (.xlsx, .xls) instead of CSV
- File is a link to an online spreadsheet rather than a downloaded file
- File is JSON, XML, or another structured format
- File extension says .csv but the actual content is a different format
How to fix it:
- Convert to CSV. Open your file in a spreadsheet application and use "Save As" or "Download" to export as CSV (Comma-delimited).
- Verify the file extension. Make sure the file name ends in
.csv. - Inspect the file contents. Open the file in a plain text editor. You should see rows of comma-separated values. If you see garbled characters or markup tags, the file is not a valid CSV.
"Encoding error detected" or garbled special characters
What this means: Your file uses a character encoding that TexAu cannot interpret, typically because it was created in a non-English locale or uses an unsupported encoding standard.
How to fix it:
-
Re-save in UTF-8 encoding.
- Open the file in a text editor that supports encoding selection.
- Change the encoding to UTF-8.
- Save the file and try importing again.
-
Remove problematic characters. If your file contains unusual symbols or non-standard characters, replace them with standard alphanumeric text.
-
Use a spreadsheet intermediary.
- Open the file in a spreadsheet application.
- Copy all data.
- Paste into a new spreadsheet.
- Download as CSV.
- This process often resolves encoding issues automatically.
"Binary file detected"
What this means: TexAu has identified the uploaded file as a binary or executable file rather than a data file.
How to fix it:
- Verify you selected the correct file. Make sure you are uploading your data CSV and not a program file (.exe, .dll, .zip, or similar).
- Re-export your CSV. Open the original data in a spreadsheet application, confirm you can see the data clearly in rows and columns, and save/download as CSV again.
- Contact support if you believe the file is a valid CSV and this error is incorrect. Include the file so we can investigate.
Enrichment not running
"Enrichment is pending but hasn't started"
What this means: You submitted data for enrichment, but processing has not begun.
Diagnosis checklist:
This table scrolls sideways on small screens.
| Check | Where to Look | What to Do |
|---|---|---|
| Required columns present | Table view —column headers | Ensure each column has a data type assigned (Email, Company Name, Phone, etc.) |
| Providers configured | Column settings —Waterfall or Data Source section | Confirm at least one provider is selected and connected |
| Credits remaining | Profile menu —Billing and Usage | If credits are at zero, purchase more or upgrade your plan |
| Plan row limit | Billing and Usage —row count | If you have reached your plan limit, upgrade to a higher tier |
How to fix it:
- No credits remaining: Purchase additional credits or upgrade to a plan with a larger monthly allotment.
- No providers configured: Go to Settings, then Integrations, and connect the data sources you need.
- Wrong data type assigned: Edit the column and select the correct semantic type.
- Row limit reached: Upgrade your plan to increase your monthly row allowance.
"Enrichment failed" or "Error during processing"
What this means: TexAu started processing your data but encountered an error and stopped.
Common causes:
- Input data is malformed or incomplete
- An external data provider is temporarily unavailable
- The enrichment timed out due to large volume
- A network interruption occurred during processing
How to fix it:
-
Check your input data. Review the rows that failed. Make sure each cell contains valid, complete data (properly formatted email addresses, real company names, correct phone numbers). Remove cells with obviously invalid data and retry.
-
Try a smaller batch. Select 10-20 rows and run the enrichment. If the smaller batch succeeds, the issue is likely data quality in certain rows rather than a system problem.
-
Wait and retry. External data providers occasionally experience downtime. Wait 5-10 minutes and try again. TexAu displays provider status in your integration settings if available.
-
Check your internet connection. A dropped connection during enrichment can cause failures. Ensure you have a stable connection before retrying.
Enrichment returning empty results
"No data found" or all results are blank
What this means: TexAu queried external data providers on your behalf but none returned results for those rows.
How to diagnose:
-
Spot-check a single row. Look at a row that returned no data. Is the input realistic and complete? For example, is the email address properly formatted? Does the company name match a real organization? Try searching for it manually online to confirm it exists.
-
Review your waterfall configuration. Check which providers are included in your waterfall. Are they appropriate for the type of data you are enriching? Do you have multiple providers configured as fallbacks?
-
Check provider connection status. Go to Settings, then Integrations. Confirm all providers show as "Connected." If any show an error, there may be an authentication or permissions issue preventing them from returning data.
How to fix it:
-
Improve input data quality. Remove entries with incomplete information (emails missing the @ symbol, phone numbers with wrong digit counts, misspelled company names). Validate critical fields against a reliable source before importing.
-
Add more providers to your waterfall. Different providers maintain different databases. Adding more providers increases the probability of finding a match. If you are only using one provider, adding even one backup can significantly improve your match rate.
-
Handle empty results in formulas. If downstream formulas depend on enrichment results, use COALESCE or IF statements to handle blank cells gracefully:
COALESCE(Provider1_Result, Provider2_Result, "Not Found") -
Set realistic expectations. Even with multiple providers, some records simply will not have data available in any provider's database. A 70-80% match rate is typical and healthy for most enrichment types.
Real-time updates not appearing
"Results are not showing up in real-time" or "I have to refresh to see new data"
What this means: TexAu pushes live updates to your browser as enrichment results come in, but those updates are not appearing.
How to fix it:
-
Refresh your browser. Press Ctrl+R (Windows) or Cmd+R (Mac). This re-establishes the live data connection.
-
Check your browser version. TexAu requires a modern browser for real-time updates.
This table scrolls sideways on small screens.
Browser Minimum Version Chrome 90+ Firefox 88+ Safari 14+ Edge 90+ If you are using an older version, update your browser. Internet Explorer is not supported.
-
Disable browser extensions temporarily. Ad blockers, privacy extensions, and VPN browser plugins can interfere with live data connections. Disable them one at a time to identify the culprit. If disabling an extension resolves the issue, add TexAu to that extension's allowlist.
-
Check your internet connection. Real-time updates require a stable connection. If you are on an unreliable network, updates may arrive late or not at all. Switch to a wired connection or a stronger signal if possible.
-
Keep the TexAu tab active. Many browsers throttle or pause background tabs to conserve resources. If you switch to another tab, TexAu's live connection may be paused. Click back to the TexAu tab to resume updates.
-
Try a different browser. If the issue persists after the steps above, test in a different browser to determine whether the problem is browser-specific.
Webhook delivery failures
"Webhook failed to deliver" or "Destination URL unreachable"
What this means: TexAu attempted to send enriched data to an external service via webhook, but the delivery did not succeed.
Diagnosis steps:
-
Test the destination URL. Copy your webhook URL and open it in a browser. If you receive a 404 error or the page does not load, the destination endpoint is not working correctly.
-
Check authentication credentials. Review your webhook settings in TexAu. If your destination requires an API key or token, verify it is current and has not expired. Regenerate it from the destination service if needed.
-
Verify the destination service is operational. Confirm the receiving service is running, accepting incoming requests, and has not changed its API requirements recently.
-
Check firewall rules. Some services block incoming webhook requests by default. Confirm your destination allows incoming POST requests from external sources.
How to fix it:
This table scrolls sideways on small screens.
| Problem | Solution |
|---|---|
| Incorrect URL | Correct typos, verify the endpoint path is accurate |
| Expired credentials | Generate new credentials from the destination service and update in TexAu |
| Destination server down | Wait for the service to recover; TexAu retries automatically |
| Firewall blocking requests | Allowlist incoming webhook requests on the destination service |
Retry behavior: TexAu automatically retries failed webhooks at increasing intervals (immediately, then after 5 minutes, then after 30 minutes, and so on). After multiple consecutive failures, the webhook is paused and you receive a notification. Fix the underlying issue and re-enable the webhook to resume delivery.
"Payload too large" or "Request rejected by destination"
What this means: The data TexAu is sending exceeds the size limit imposed by the destination service.
How to fix it:
-
Reduce the data per webhook. Select only the columns the destination needs rather than sending all columns. Sending fewer rows per batch also reduces payload size.
-
Check the destination's size limits. Different services accept different maximum payload sizes. Review the destination service's documentation for their webhook or API payload limits.
-
Use a processing action to format data. Instead of sending raw enrichment results, use a processing action to extract and format only the fields your destination requires. This keeps payloads compact and focused.
Formula errors
"Formula syntax error" or "Invalid formula"
What this means: The formula you entered does not follow TexAu's syntax rules.
Common mistakes and corrections:
This table scrolls sideways on small screens.
| Mistake | Incorrect | Correct |
|---|---|---|
| Missing parentheses | IF A1 = "test", "yes", "no" | IF(A1 = "test", "yes", "no") |
| Unquoted text values | IF(Status = active) | IF(Status = "active") |
| Letter-based cell references | SUM(A1, B2, C3) | SUM(Revenue, Additional_Income) |
| Unmatched quotes | CONCAT(First_Name, " ", Last_Name) (with mismatched quote types) | CONCAT(First_Name, " ", Last_Name) (use consistent straight quotes) |
How to fix it:
- Read the error message. Click the error indicator next to your formula. It typically identifies the exact position and nature of the syntax problem.
- Use the formula builder. The visual formula builder prevents most syntax errors by providing a point-and-click interface for functions and column references.
- Test with sample data. Before applying a formula to all rows, test it on a single row to catch mistakes early.
- Build incrementally. Start with the simplest possible version of your formula. Once it works, add complexity one function at a time.
"Referencing a column that doesn't exist"
What this means: Your formula references a column name that is not present in your table.
How to fix it:
- Check spelling and capitalization. Column names are case-sensitive.
Emailandemailare treated as different columns. - Use the column dropdown. When building a formula, select columns from the dropdown menu instead of typing names manually. This ensures you reference real columns.
- Handle column names with spaces. Column names that contain spaces must be enclosed in quotes:
"First Name", notFirst Name. - Verify the column exists. Navigate to your table and confirm the column is present. It may have been renamed or deleted.
"Type mismatch" or "Cannot compare text and number"
What this means: Your formula attempts to compare or combine incompatible data types, such as comparing a text value to a number.
How to fix it:
-
Identify the data types involved. Check the column types in your table. A column labeled as "Text" cannot be directly compared with a numeric operation.
-
Use conversion functions.
- Convert number to text:
TEXT(Revenue) - Convert text to number:
VALUE(Age_Text) - Example:
IF(VALUE(Age) > 21, "adult", "minor")
- Convert number to text:
-
Ensure comparisons use matching types.
- Compare text to text:
IF(Status = "active", ...) - Compare numbers to numbers:
IF(Revenue > 50000, ...) - Do not mix:
IF(Revenue > "50000", ...)—this compares a number to text
- Compare text to text:
"Division by zero error"
What this means: Your formula divides by zero or by an empty cell, which is mathematically undefined.
How to fix it:
-
Guard against zero with an IF statement:
IF(Denominator = 0, 0, Numerator / Denominator) -
Guard against empty cells with COALESCE:
IF(COALESCE(Denominator, 0) = 0, 0, Numerator / COALESCE(Denominator, 1)) -
Review your input data. If the column you are dividing by is mostly empty, you will see this error on most rows. Ensure the column is populated with valid numeric values before running formulas that depend on it.
Scheduled job not running
"My scheduled enrichment didn't run at the expected time"
What this means: A recurring enrichment you configured did not execute on schedule.
Diagnosis checklist:
This table scrolls sideways on small screens.
| Check | How to Verify | Resolution |
|---|---|---|
| Schedule is active | Table view —Schedules section —check toggle is ON | Toggle the schedule ON |
| Correct timezone | Settings —Account —Timezone | Set timezone to your actual location |
| Plan limit not exceeded | Billing and Usage —monthly row count | Upgrade plan if limit reached |
| New data exists | Table view —check for unenriched rows | Import new data or reset enrichment status on existing rows |
Detailed steps:
-
Check if the schedule is paused. Navigate to your table, open the Schedules section, and verify the schedule is toggled ON. Paused schedules do not execute.
-
Verify the timezone. Open Settings, then Account, and confirm your timezone is set correctly. Scheduled times are displayed in your configured timezone but stored internally in UTC. If your timezone is wrong, the schedule runs at a different time than you expect.
-
Review plan limits. Open Billing and Usage and check your monthly row count. If you have reached your plan's limit, scheduled jobs will not run until the next billing cycle or until you upgrade.
-
Confirm there is data to process. Schedules only enrich rows that have not already been enriched. If all rows in your table already have enrichment results, the schedule has nothing to process. Import new rows or manually clear enrichment status on rows you want to re-process.
Integration connection issues
"Integration disconnected" or "Credentials expired"
What this means: TexAu has lost its connection to an external data provider or service.
Common causes:
- Your API key, token, or access grant has expired
- You changed your password on the external service without updating TexAu
- The external service revoked access or changed its authentication requirements
- Your account on the external service was deactivated
How to fix it:
-
Reconnect the integration. Go to Settings, then Integrations. Find the disconnected service and click "Reconnect" or remove and re-add it.
-
Re-authenticate. If the integration uses a login-based connection, click the connect button again and sign in. If it uses an API key, generate a fresh key from the external service's settings and enter it in TexAu.
-
Check permissions. Confirm your account on the external service has the necessary permissions to generate API keys and access the required data. If you use a shared or team account, ask your administrator.
-
Contact the external service. If reconnection fails repeatedly, the external service may have changed their requirements. Check their documentation or contact their support team.
"Permissions error" or "Access denied"
What this means: The connection to the external service is active, but your account lacks permission to access the specific resources TexAu needs.
How to fix it:
-
Request elevated permissions. Contact your administrator on the external service and ask for the access level TexAu requires (typically read access to contacts, companies, or similar data).
-
Use a dedicated service account. Instead of your personal account, create a service account with the specific permissions TexAu needs. Use that account's credentials in TexAu.
-
Check the external service's plan. Some features on external services are only available on certain plan tiers. Verify your subscription level includes API access.
Slow performance
"TexAu is running slowly" or "Enrichment is taking a long time"
What this means: Processing is taking longer than expected.
Common causes and optimization strategies:
This table scrolls sideways on small screens.
| Cause | Optimization |
|---|---|
| Very large table (100,000+ rows) | Enrich in batches of 10,000-20,000 rows |
| Multiple enrichments running simultaneously | Run one enrichment at a time; wait for completion before starting the next |
| Complex nested formulas | Break into multiple simpler formula columns; use processing actions for heavy transformations |
| Slow network connection | Use a wired connection; avoid enrichment over mobile data |
| Peak usage hours | Schedule large enrichments for evenings or weekends |
Detailed recommendations:
-
Batch your data. Instead of enriching an entire large table at once, select subsets and process them sequentially. This reduces memory usage and improves completion speed.
-
Limit concurrent enrichments. Running multiple enrichments in parallel on the same table can slow each one down. Complete one before starting another.
-
Simplify formulas. Deeply nested formulas (more than 3-4 levels of nesting) are computationally expensive. Break them into intermediate columns with simpler formulas. For example, instead of:
IF(AND(A=1, B=2, C=3, D=4), "Match", "No Match")Create separate flag columns for each condition, then combine them.
-
Reorder your waterfall. Place faster-responding providers earlier in your waterfall. This reduces average wait time per row.
-
Archive old data. If your table contains historical rows you no longer need to enrich, move them to an archive table to reduce the working set size.
-
Use off-peak scheduling. Large enrichments run faster during evenings and weekends when system load is lower.
-
Contact support. If performance issues persist after optimization, reach out with your table name and approximate row count. We have additional options available for high-volume use cases.
Still stuck?
If your issue is not covered above, our support team can help. When you contact us, include the following so we can look into it quickly:
- A description of the problem: what were you trying to do, and what happened instead?
- Screenshots of any error messages, including the exact wording and any error codes.
- Your table name, so we can locate your data in our system.
- When the problem started (date and approximate time).
- What you have already tried.
How to reach us:
- In-app support: click the help icon in TexAu to open a support chat.
- Email: support@texau.com. We typically respond within a few hours during business days.
Next steps
- Frequently Asked Questions for answers to common questions.
- Best Practices Guide for tips on getting more out of TexAu.
- The Help Center home page for more guides and tutorials.