One of the most common causes of errors in TexAu comes when you don't set up all your social media account in English as the primary language.
The reason is that social media page source code and selectors often differ from one language to another. For example, TexAu works in the English language only.
You can learn how to set up your language in your account preferences here:
In every automation, there is an indication about the expected input:
In the above example, a LinkedIn company URL is the URL of the company profile page on LinkedIn, not the website domain. It's often easy to make such confusion.
Pay attention to these indications, and be sure to input to correct URL format to ensure optimal results.
Last, ensure you don't add any space before or after your URL! It sounds stupid, but this happens more than often 😉.
Another source of errors can come from using the wrong automation, and confusing it with another one.
For example, many people confuse Sales Navigator Leads List with Leads Search:
LinkedIn Sales Navigator Lead Lists are profiles that you manually pick and sort as lists.
LinkedIn Sales Navigator Leads Search is the profile search.
The same goes with Widthdraw LinkedIn Connection Request and Connection Remover:
Withdraw pending connection request:
Here you will withdraw LinkedIn pending connection requests (the one waiting for approval).
Here you will remove profiles from your 1st-degree connection network (be careful!).
Many people activate the setting "Process only new results," thinking it's about output deduplication while it is not.
That setting serves the purpose of deduplicating URL inputs. The practical use case is when you run a Drip Campaign workflow, and you don't want to send twice the same message to a list of prospects. This setting will remove any duplicate URL inputs, so TexAu only processes unique profiles in the campaign.
So you may encounter this in the logs when this setting is on:
To overcome this, uncheck the box "Process only new results":
Another error you might encounter is when some profiles on LinkedIn Search are outside of your network like that one:
It's not either a 1st, 2nd, or 3rd-degree connection, and you cannot see the profile except in the LinkedIn search listings:
So when you are scraping such profiles from the LinkedIn search results, you will get this error message displaying in the automation or workflow result section:
Also, the same will happen if the profile is private:
Sadly, there is nothing you can do in this case. The profile isn't accessible from your network.
When running the same input in the same automation or workflow at different intervals (scheduled or run manually), you will see this message in the logs: "Continuing old execution".
This process occurs in automation or workflows with recurring schedules. That way, TexAu will always restart the automation or workflows at the last step it was processing in the schedule. A practical example of this is when you want to scrape daily new Twitter or Instagram account followers.
That means TexAu will keep in memory the old results from past execution as long as the old logs are there in the "Results" menu:
But sometimes, you want to start fresh and only run a automation or workflow from scratch every time to collect the latest results only.
To overcome this, you will have to all delete past executions of the same automation or workflow having the same input, including all past schedules:
Again, this is only valid if those automation or workflows have the same input. This process won't be necessary if you process different executions with different input URLs (or different CSV or Google Sheets URL lists each time) using the same automation or workflow.
On some rare occasions (TexAu downtime, bug) your workflows and their schedules may stop.
If this occurs, there is a simple procedure to follow to restart them.
First, pause each scheduled execution, one by one:
Second, restart each schedule one by one by hitting the play button again. After some time it will restart following the same schedule:
If your workflow has routes (two-way branches using conditions), you must follow the same above procedure:
If your cookie expires after a few days or weeks, you can restart your workflow following the same procedure described above.
Here, you must update each schedule manually, one by one, and input a new cookie.
If you entered your cookies in the cookie manager, you must update your cookie there.
Once done, hit the play button for each schedule to restart the automation.
Another LinkedIn related error message you may see in TexAu logs:
- The profile connected with you already (1st-degree connection)
- Your connection request is still pending
- Out of network profiles (people no one is connected to in your network, not be confused by 3rd-degree connections)
Another cause of LinkedIn missing "connect" button on target profile:
Still, it can sometimes happen to be a bug. So the best way to know what's happening is actually to look at the logs. Check the row number on your Sheet or the profile URL that returns the error and opens the page. Contact us via support if you can see the "connect" button on the LinkedIn profile page and still can't send a connection request to that profile.
Another error message you may experience:
The above usually happens when your LinkedIn account language isn't English. However, don't hesitate to contact support if you have already put all your social accounts in English and none of the above works.
Another common issue is when scraping a LinkedIn search results doesn't return all the page results:
What often happens is that if you are using a free LinkedIn account, you may have reached your search limit monthly quota. Unfortunately, these limits depend on your account activity and history, and there is no official number for this.
You can see this by looking at your LinkedIn account here:
Probably the number cause of issues you may encounter in TexAu. Invalid cookie messages can happen for multiple reasons:
- You use TexAu Cloud (browser version) without a proxy and switch between your current location and TexAu servers' IP, which leads your cookies to disconnect.
- Same as above but switching between your actual location and your proxy location.
- You scrape too much data in a short period. Such disconnections can happen for search URLs, Group members, or Profile Followers intensive scraping.
In all the above cases, all you have to do is to update your session cookies by using the TexAu chrome extension and submit the new value:
If the problem persists and you are sure not to have made too much automation, contact support to investigate the matter.
Sometimes when trying to use one of our integration requiring API keys, you may encounter this error message in the logs:
Be sure to check if your API Keys are valid and entered correctly in the corresponding fields.
You may also see a message like this:
This error message means there must be an API rate limiting issue due to an evolution of the integration API or that the integration service is down (yes, this can happen sometimes).
If that's the case, please get in touch with support.
These messages aren't errors per se but indicate that you reached the daily safety limit for one automation. This limit will apply whether you use a single automation or because one of the automation in your workflow reaches its daily limit.
When this happens, you will have to wait for 24 hours or use another account to run your automation or workflow:
For Instagram, you may have a similar error message when you are scraping too much data like followers in a too short time:
That means you probably reach the Instagram rate limit. Wait for a minimum of 15 minutes, then retry.
If the problem persists, be sure to log in to your Instagram account to ensure all is ok (no warnings). If that's ok, then wait for a few days and retry.
If none of the above works, please get in touch with support.
Another standard log message is when you reach your daily execution time limit:
In this case, you will have to wait at midnight according to the time zone you set in TexAu preferences, so your daily execution limit can refill for the next 24 hours.
Another common cause of issues you may experience is related to Google Sheets.
Here is a checklist of all the things you must do before reaching:
You Sheet should not be empty! Be sure to have at least the first cell of the Sheet filled with data.
Another common mistake is to have a Sheet with twice the same header name, which won't work. Instead, all header names for each column of your Sheet should be unique. Otherwise, Google Sheet API can't read the Sheet properly.
For Google Sheet output, be sure to follow this checklist:
- no duplicate header column name: all header names should be unique (same as with inputs).
- If you map more than 26 columns (range A to Z - Sheet defaults), be sure to increase the number of total columns on your Sheet to match the number of mapped columns in TexAu. Otherwise, you won't be able to write on the Sheet.
- Be sure to set the appropriate Google Drive permission for TexAu access so you can read and write on your Sheets.
For more information about this, read these two articles:
While the Desktop App is convenient because it can run on your local machine and doesn't require any proxy, there are some downsides:
- Since it doesn't run continuously, waking your computer from sleep can sometimes need an app or computer restart to work correctly.
- Overall it's less stable than the cloud version because the infrastructure is less predictable: one app installed on dozen of different computer configurations vs. one predictable infrastructure common to all in the cloud.
Ad blockers like Adguard which installs locally and acts at the device level can cause issues with automation operations like scraping Facebook Ad Library or Google Ads.
Please consider turning it off temporarily when you use the TexAu desktop for these tasks.
The following Desktop App related messages are pretty common too.
Desktop App closed or computer shut down:
Desktop App closed because of computer sleep or laptop lid closed:
To restart these executions, restart the desktop app, and it should continue after a few minutes. If it doesn't, resume the execution and release the pause button from the Results menu logs.
Depending on your TexAu plan, you are allowed only a limited number of computers to install and run TexAu Desktop App.
If you exceed the maximum number of machines allowed, you'll see the message below:
To overcome this:
- log off your old machine (if you intended to install TexAu Desktop App on a new device)
- Then contact support to reset your machines so you can install your license to a new computer.
Later on, you will be able to do this without support intervention via an online self-service portal.
The following error message logs are likely to be related to bugs you may experience with the platform when a social media page code changes and our development team will have to release a fix for it.
If all the above in this article didn't solve your issues, please contact us via support.
The following error messages are likely bugs (providing you did the previous checks above), and you definitely should contact support 🥶:
You may have randomly experienced this:
Single automation or workflows executions that get stuck indefinitely sitting in orange in your logs. Those are probably "dry runs" that never launched.
Sadly there is no way to delete those logs except to erase them from our database.
This bug is purely cosmetic and happens rarely. However, we will try to find a way to avoid this in the future.
Some adblockers chrome extensions can interfere with your experience using TexAu. Also, extensions like Grammarly or any extensions that interact with the page's code can cause similar issues.
For that reason, we recommend deactivating those extensions in your browser only for TexAu.
You can exclude the TexAu domain from those extension filters and keep it active for other websites, but not with TexAu.
You may encounter this cosmetic bug on rare occasions:
This bug can happen for two reasons:
- cosmetic bug: click on another automation and click again on the current message automation where the issue occurred. The variable should reappear again.
- You removed a previous module in a workflow, hence the variable disappearing: in this case, you will have to add the variable again in your module.