A: Hi,

For support questions, please join our Discord community at https://community.robomotion.io.

1–2. Cloud Robots Environment
Cloud robots run inside a Linux-based Docker container, so file paths differ from those on Windows. Some desktop-dependent packages will not function, as there is no graphical desktop environment. However, browser automation and does work because it uses headless Chrome. So only a few packages that require a full desktop environment may not work.

To assist you further, we need to review your flow and the exact exception you're encountering. Feel free to share screenshots in our Discord support channel.

Cloud Run Usage and Stop Node Requirement

Cloud Run consumes minutes as long as the robot is running. Regardless of whether it was started by a trigger or a schedule, you must include a Stop Node in your flow to stop the robot once processing is complete.

Note about Webhooks:

Mail, Queue, and File System triggers are supported in Cloud Run. However, HTTP Handlers are not currently supported. Our "HTTP In" nodes (synchronous web request handlers) and HTTP Post via Queue (asynchronous web request handlers) require a public IP and Port. As a result, they can only be executed on machines that are directly accessible from the internet not from within a Cloud Run environment.

We are currently rewriting all our platfrom products from scratch. We have renewed nearly everything to be more AI compatible and prompt friendly. We are releasing our new designer this week. After this a more user friendly webhook is in our roadmap that will also be available to be used with our Cloud Run feature.

Best,