What are the features and limitations of a Community license on BotCity Orchestrator?
A new account that is created on BotCity Orchestrator has full access to the platform's functionalities (trial) for a period of 30 days.
After this 30-day period, access to the platform continues in the same way; the only differences are some limitations and access to some specific resources.
After the trial period, it is no longer possible to use the following features:
- Datapool
- Schedules
- Credentials
Additionally, the workspace will also have some limitations on other features:
- Tasks - maximum of 10 tasks created per day
- Automations - maximum of 1 automation process on the platform
- Runners - maximum of 1 Desktop Runner on the platform
You can find more details about the difference between the plans and available resources by accessing this link.
Info:
The limitations of a Community license are focused on the orchestration step using the BotCity Orchestrator.
The automation development stage does not have any limitations regarding the use of BotCity frameworks and plugins.
Related Articles
Where can I find content to learn more about using BotCity?
A great alternative to have a first contact with the tools is to access the courses available on BotCity Academy. Additionally, you can also access the tutorials available on the documentation portal: Getting started with BotCity Developing your ...Problems with blocking environments
If you are trying to use BotCity's tools in a corporate environment, you may encounter some issues related to environment locks. Here are some of the most common issues when using the BotCity Studio SDK in blocking environments: Installation through ...How to open a support ticket?
If the knowledge base articles or our documentation portal did not resolve your questions or issues, you can open a new support ticket through the portal. After detailing the type of support you need, the ticket will be directed to our team so that ...Problems with dependencies when running an automation
This problem usually occurs when the dependencies installation step is not done correctly. When running the code, a message is displayed regarding the installation of the packages: ModuleNotFoundError: No module named 'botcity’ The first step is to ...Keeping your remote session active when using Runner
In some cases where a VM is used to run the automation, keeping the remote session active is necessary to avoid problems with the graphical interface, such as the OSError: screen grab failed error. This error is usually thrown when trying to perform ...