We're excited to announce the launch of Robomotion v24.4.0! This version includes crucial bug fixes, visual and usability improvements, and technical adjustments. Key highlights include resolving two significant issues: one related to a PATH problem on Windows that was causing issues with starting robots, and the other addressing a race condition that occasionally froze the robot state when starting pending schedules. Additionally, we've refreshed the visuals of the Flow Designer, fixed and fine-tuned the colors of the Dark Mode.

Here’s what’s new in version 24.4.0:

🚨 [Fixed] We've resolved the Windows Desktop PATH issue that was preventing robots from starting. Our launch.exe workaround has been removed from this release. The root cause of the problem, which we recently discovered, was a breaking change introduced by Golang v1.19 in "PATH lookups." For more information, visit: https://tip.golang.org/doc/go1.19.

🚨 [Fixed] We've resolved a race condition where, in rare instances, a pending schedule combined with the closing of a previous flow's nodes would halt the newly started pending schedule, leaving the robot unable to continue.

✅ [Fixed] Fixed status update notifications for Publishing and Creating versions now accurately reflect the process completion.

🚫 [Fixed] Instances now properly show as stopped when crashed, avoiding misleading 'Running' status.

👀 [Fixed] Admins can now see all running instances, correcting a previous limitation to only workspace Owners.

🔄 [Updated] We've renamed "Desktop Run" to "Local Run" to more accurately represent wide-range of robot installations across VPS, Dedicated Servers, and Desktops.

📈 [Fixed] We've fixed the handling of traffic from non-registered workspace users on "publicly shared" apps, which previously led to consistent flow failures during periods of increased usage.

🌙 [Improved] Flow Designer UI is updated and especially the Dark Mode received fixes and updates.

🆕 [Added] New $RunType$ global variable to distinguish between "cloud" or "local" runs easily.

📧 [Fixed] Invite and Join workspace processes no longer accept email addresses with spaces, preventing login issues.

🔢 [Improved] Cloud Credit multipliers were confusing, particularly for the default apps in our App Store, most of which use 2 vCPU and 4 GB RAM. We've adjusted this configuration multiplier to 1x, ensuring usage is deducted based on real-time clock usage. Now, 1 vCPU and 2GB RAM have a 0.5x multiplier, 4 vCPU and 8 GB RAM have a 2x multiplier, and 8 vCPU and 16 GB RAM have a 3x multiplier of the real-time clock consumed.

💳 [Added] Cloud Run Pricing information is now accessible through the Admin Console under the Subscriptions "Buy More" option.

🔄 [Added] We've added checkboxes for required add-ons such as Proxy Request and AI Credits on the App Publish page. This update will help checking the requirements essential for a one-click start of the app.