10.1.4.1

Edit

‎Troubleshoot Control Tower issues

Unexpected results after Crowd deletion

Expand to learn more

Scenario 1

The steps below describe Scenario 1 how the issue can occur:

  1. Go to Workers > Workforces > Manage Crowds.

  2. Create a Crowd.

  3. Assign a Qualification to it.

  4. Remove the Crowd.

    note

    At the step, there is no check that the Crowd has an assigned Qualification.

  5. Refresh the page and open Manage Crowds again.

    You can see the actual number of Crowds in the list is not the same as shown in Manage Crowds (No).

  6. Connect to the wfdb database.

    mysql> SELECT name, CAST(deleted AS UNSIGNED) AS deleted FROM Crowd;
+-----------------------+---------+
| name                  | deleted |
+-----------------------+---------+
| Local Workspace Crowd |       0 |
| test_crowd2           |       1 | <<<<<
+-----------------------+---------+

In the case of deleted=1, the Crowd is not visible in the UI, so update its value directly in the table.

Scenario 2

The steps below describe Scenario 2 how the issue can occur:

  1. Go to the Qualification assigned to the already deleted Crowd.

  2. Try to remove it. The following error is shown:

    Can not remove qualification: TestQualification1. It is used in crowds: [test_crowd2]

Resolution

To resolve the issue, follow the instruction below:

  1. In the database, check the status of the required Crowd.

    SELECT name, CAST(deleted AS UNSIGNED) AS deleted FROM Crowd;
+-----------------------+---------+
| name                  | deleted |
+-----------------------+---------+
| Local Workspace Crowd |       0 |
| test_crowd2           |       1 |
+-----------------------+---------+

  2. In the Crowd table, update the deleted field.

    update Crowd SET deleted=b'0' where name="test_crowd2";
    note

    The step is applicable for v9.x only. Skip for v10.x.

  3. Go to Manage Crowds. The affected Crowd should be present in the list. Unassign the qualification to this Crowd.

  4. Remove the Crowd. The Qualification should be removed without issues.

LDAP AD authentifications do not work with + or % symbol in passwords of Control Tower users

Expand to learn more

Symptoms

When a LDAP/AD user tries to log into the Control Tower UI, you can observe the following error:

The Control Tower user account is not locked or disabled, but there is a "+" or "%" symbol in the password.

Resolution

When creating passwords, make sure they are strong enough and meet the following requirements:

# - must be used standard English symbols
# - must be no shorter than 6 symbols and not longer than 20 symbols;
# - must contain at least one uppercase character [A-Z]
# - must contain at least one lowercase character [a-z]
# - must contain at least one numeric character [0-9]
# - must contain at least one of the following special symbols unless limitations are explicitly described in comments: @#^*():,.}[]<>/
# - must NOT contain the following symbols: ;\"!?&'{$|`%
# - must NOT contain spaces

The "+" and "%" symbols are out of the special symbol list allowed in the passwords of Control Tower users. The complete list of allowed symbols is as follows:

@#^*(),.;}[]<>/

It is mentioned in the $INSTALL_DIR/wf_installer/config.yml file located on the APP server. The Control Tower default user credentials used for login into the Control Tower UI from a browser:

wf_username: 'workfusion'
wf_password: '**********' # Allowed special symbols: @#^*(),.;}[]<>/

These restrictions were changed in Intelligent Automation Cloud Enterprise v10.1.6 and further versions:

  • For mssql_dm_pass and mssql_rapi_pass passwords, permitted symbols are as follows:

    %^#*@/\`+-=_&$()[]:,.;!?

    Forbidden symbols:

    {}'<>"|

  • For all other application passwords, permitted symbols are as follows:

    %^#*@/\|`+-=_<>&$(){}[]:,.;!?

    Forbidden symbols:

    " '

Getting 503 error for your instance

Problem 1: Control Tower is not working and getting 503 error

Expand to learn more

There is no space on the INT server. Delete unwanted files. For more details, refer to Scheduling jobs.

Problem 2: Elasticsearch size keeps growing

Expand to learn more

Symptoms

You get the following error:

Caused by: org.elasticsearch.common.ValidationException: Validation Failed: 1: this action would add [1] total shards, but this cluster currently has [1000]/[1000] maximum shards open; org.elasticsearch.xpack.monitoring.exporter.ExportException: org.elasticsearch.common.ValidationException: Validation Failed: 1: this action would add [1] total shards, but this cluster currently has [1000]/[1000] maximum shards open; Caused by: org.elasticsearch.common.ValidationException: Validation Failed: 1: this action would add [1] total shards, but this cluster currently has [1000]/[1000] maximum shards open;

Resolution

To resolve the issue, increase the shards using the following command:

curl -u 'admin:sc@********' -k -X PUT https://10.12.4.144:9200/_cluster/settings -H "Content-Type: application/json" -d '{ "persistent": { "cluster.max_shards_per_node": "5000" } }'

← Worker utilizationModify JVM properties →