Troubleshooting

Many common errors produced while using the State Tool can be resolved by either pushing your local changes to the Platform, or pulling down changes from the Platform to your local machine.

  1. To push the local settings of your activated project to the Platform run state push.
  2. To pull changes in the Platform to your activated project run state pull.

Any trouble with “lagging” or “hanging” projects can be solved by closing your command line and re-opening and activating your project using the state use <orgname>/<projectname> command, or opening a new shell by running state shell <orgname>/<projectname>.

State Tool issues

If you encounter errors when using the State Tool, please reach out to our support team at support@activestate.com. The more information you can provide them with, the sooner your issue can be reproduced and resolved. Please provide the following information, where possible:

  • A short summary of the issue
  • Step steps to reproduce
  • Expected result
  • Actual result
  • Logs (if relevant)

The State Tool logs are stored in the following locations by default:

  • Windows: C:\Users\<User>\AppData\Roaming\activestate\cli-unstable\log.txt
  • Linux: ~/.config/activestate/cli-unstable/log.txt
  • macOS: ~/Library/Application Support/activestate/cli-unstable\log.txt

More Troubleshooting