General

The errors listed below are general occurring errors.

# Internal server error


Error: Internal server error.

Problem: If you are seeing this within the extension, or when you use the 'run in cloud' option, we may be experiencing issues. If you are seeing this on a page not associated with axiom.ai, you will need to contact the owner of the page for more details.

Fix: Our team are likely already working on a resolution, if this continues, contact us (opens new window).

# This step does not exist in your version of the Axiom.ai desktop application


Problem: There may be a mismatch between the version of axiom.ai's desktop application that you have installed and the automation that you are running.

Fix: Update your desktop application by opening it. Look for update prompts within your automation to update steps to the latest version.

# Concurrency limit reached


Error: All of your bot allocations are currently in use! Click below to stop them, or wait for them to finish.

Problem: Your account has hit it's concurrency limit, see the pricing page (opens new window) for more details on your account concurrency limit.

Fix: Wait for your running bots to finish, or upgrade your account for more concurrency.

# Cloud servers busy


Error: Oh no, all our cloud servers are busy right now!

Problem: This is very rare, our servers have hit their capacity.

Fix: Try again in a few minutes, or use the desktop app (opens new window) to run your automation locally.

# Browser could not be started


Error: Browser could not be started. This is may be an incompatibility between the Axiom desktop application and your operating system. Please contact support@axiom.ai and let us know about the issue! This error can also occur on Mac if you have tried to load a missing or broken extension.

Problem: There are multiple potential causes to this error, including:

  • An incompatibility between the Axiom desktop application and your operating system.
  • Settings in your automation pointing towards an incorrect Chrome executable path.
  • Settings in your automation pointing towards a missing or broken Chrome extension.
  • A hanging Axiom.ai process on your machine.

Fix: Listed in the order of potential problems:

  • Ensure your operating system is up to date, older versions of operating systems may not be compatible with Axiom desktop.
  • Ensure that your Chrome instance path is correct, see set executable path for more details.
  • Ensure that any Chrome extension added is installed, and the path is correct, see load another extension for more details.
  • Restart your computer.

# Port in use


Error: Port in use: {port}

Problem: Axiom.ai has tried to run on a port that is already in use on your computer.

Fix: Disable the application running on the post noted in the error, close the Axiom.ai desktop application and reopen it to continue.