CloudShell Version: 9.3

Release Notes Version: 7.0

You are here: Overview > Known Limitations

Known Limitations

This section describes known limitations of CloudShell Pro, as well as possible workarounds for these issues when available.

Issue	Solution
Job Scheduling UI: Adding tests to a suite containing a large number of tests with inputs may take longer than expected.	Use the New Job Scheduling, which was released with CloudShell 2021.1. It has been developed specifically to accommodate high-load scenarios.
For customers who are: Upgrading from CloudShell Pro version 9.0 or earlier to version 9.1 or later -and- Have blueprints that contain abstract resources with published attributes -and- Are using Job Scheduling Job suites with published inputs using above mentioned blueprints will fail and all published inputs may be lost.	1. Upgrade to the latest available CloudShell version only. 2. Contact your customer success representative to perform a required manual update to all job suites.
In Resource Manager client, when editing the “Max Scheduled Sandboxes” for a user multiple times, the last valid value is saved.	Enter a numeric value only
In the Job Scheduling dashboard, when the user attempts to run a test suite during which the user exceeds the maximum number of scheduled sandboxes s/he’s permitted to schedule, a wrong error message is displayed in the cancelled job.	The user should avoid exceeding his/her permitted number of sandboxes.
Resource, App and Service attribute names can contain alphanumeric characters and spaces only. When importing resource families to CloudShell Pro through Resource Manager Client, this issue is not enforced and an error message will not appear. However, referencing imported attributes whose names contain unsupported characters may cause unexpected behavior.	Before importing packages or the system.xml configuration file, review all attribute names.
Using the packaging API, it is possible to add the following to a blueprint: shared sub-resources that are added to an unshared resource. This is not possible through the Resource Manager client.
Using the API, when the config key “PickOnlyUsersFromLoggedInUserGroups” is set to “true”, the sandbox owner can be changed to a user which is outside of the user group of the current owner. When this key is set to "true" the changeowner API is not enforced by the key and the behavior is undefined.
Using the API, when the config key “PickOnlyLoggedInUser” is set to “true”, the sandbox owner can be changed to a user other than himself. When this key is set to "true" the changeowner API is not enforced by the key and the behavior is undefined.
The Linux Execution Server installation script fails when executed on a Linux operation system with an existing installation of python 3 with symlink to usr/bin/python3.	Remove the symlink from usr/bin/python3 by running the following cmd: `rm –f /usr/bin/python3`. Run the Installation script again.
In some cases, in the Job Scheduling dashboard, a suite's status may appear as "in process" while its jobs have already ended.	If you are experiencing this issue, please open a support ticket.