Skip to main content

Configuration Issues

Lior Neudorfer avatar
Written by Lior Neudorfer
Updated over 10 months ago

When fetching your environment, Salto may encounter some issues which prevent a fully successful fetch. These issues are listed in the "Configuration Issues" screen, accessible from the top-right corner of your environment view:

In this screen, you can view all configuration issues, and get more details about each one by clicking on them. In case these issues affect a specific configuration element, clicking on them will also show you the affected element.

We recommend users to review and fix Configuration Issues early on, as some of them may prevent successful deployments.

Common configuration issues

The common issues users encounter are:

  1. Credential issues

    1. Salto could not access the application configuration, as the supplied credentials were incorrect or expired. Make sure your credentials are set correctly by following these instructions

  2. Permission and access problems

    1. Salto could not access some parts of the configuration, due to permission issues. This usually means that the user credentials have missing permissions configured on the application side; fix those and try fetching again

  3. ID collisions

    1. This issue indicates that multiple application configuration elements were assigned the same Salto Element ID, which prevented them from being fetched. Read more about this problem and solutions in this article.

  4. Missing References

    1. This issue indicated that an element contains a reference to another element, which does not exist in the Salto environment. This can be a result of an ID collision which prevented an element from being fetched, or simply a broken reference in the application itself (for example, an automation which still points to some field deleted in the past).

  5. Invalid Configuration

    1. This issue means that some invalid configuration was made in your environment configuration file. Access the file by clicking this issue and fix the problem.

There are additional, less common issues that users may encounter. Follow the instructions on the issue itself to understand and fix it.

Did this answer your question?