Catalyze CLI Troubleshooting

Catalyze CLI Troubleshooting


bash: catalyze: command not found

  • Potential Issue: You have not added the Catalyze CLI binary to your PATH environment variable.
  • Potential Solution: You can add the Catalyze CLI to your PATH environment variable by running export PATH=$PATH:/path/to/your/catalyze/cli/binary or adding that line to your bash profile.


[fatal] A required update has been applied. Please re-run this command.

  • Potential Issue: Your user cannot write to the file or directory the Catalyze CLI binary is stored in.
  • Potential Solution: sudo chown -R $(whoami) /path/to/your/cli/binary If this doesn’t work you can uninstall and reinstall the CLI.

Pod ID Not Found

fatal (0) Pod ID Not Found: Invalid Pod ID specified in X-Pod-ID header

  • Potential Issue: The Catalyze CLI references a configuration file ~/.catalyze to cache configuration data. This configuration file may contain old configuration information that may need to be updated.
  • Potential Solution: To erase all or some cached configuration data you can use the catalyze clear command.


fatal (92005) Console Setup Error: {“code”:500,“error”:“Internal Error”}

  • Potential Issue: You are trying to connect and run a console command on a job that is not running or a code service that has failed to build and deploy.
  • Potential Solution: Ensure that the service you are trying to run a console command for has jobs that are running. You can check the status of your services by using the Catalyze CLI command catalyze status. If you have ensured that your service is running and you are still receiving this error, contact Catalyze support.

(0) Command Not Authorized: The command supplied is not a whitelisted command

  • Issue: The console command you are trying to run is not in the whitelist.
    -Solution Catalyze whitelists commands that you are able to run for security purposes. Contact Catalyze support to request a command be added to the whitelist.


You do not have access to the requested repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

  • Potential Issue: You are using a deploy key from a different environment.
  • Potential Solution: Set up user keys as a replacement for deploy keys. User keys are associated with your user and will work on any environment. See this guide for instructions on setting up user keys.

Cloud computing for healthcare

If you store, process, or transmit Protected Health Information, rely on Catalyze to keep you HIPAA compliant with our platform as a service, mobile backend, or managed HL7 integrations.

Contact Us Learn More

Catalyze learning resources

Learn the important and intracate details of HIPAA compliance, make use of HL7, and understand the security aspects of handling protected health information with our learning resources.

Visit Catalyze Learning Resources