Robocorp 3.1.2 and robocorp-log 3.1.3
Control Room API request timeout
robocorp-vault, robocorp-workitems and robocorp-storage now apply a default 60-second request timeout to Control Room API calls (#484).
Previously these calls were made without an explicit timeout, so requests would wait indefinitely for a response. A stalled connection — one dropped by a proxy or load balancer, for instance — hung the run forever instead of raising and letting the existing retry logic take over. With a timeout in place the request fails, retries, and the task can make progress.
The value is configurable through the RC_API_REQUEST_TIMEOUT environment variable. Set it in your run environment (the env section of robot.yaml, or a Control Room environment variable) — that is the normal place for it.
It is read once when the module is imported, so if you do set it from Python it has to happen before the import:
Robocorp Log
robocorp-log 3.1.3 fixes 13 npm security vulnerabilities in the React application that renders the log output (#473), affecting dompurify, vite, lodash, flatted, picomatch, postcss, brace-expansion and tmp.
dompurifybumped to ^3.4.0 andviteto ^6.4.2- npm overrides added to pull in fixed versions of transitive dependencies
- The embedded React output view was rebuilt, so
log.htmlfiles produced by this version carry the fixed bundle
Robocorp Windows
robocorp-windows 1.1.2 fixes wait_for_condition() ignoring the caller-supplied timeout and always waiting 8 seconds (#480). This release shipped slightly ahead of the rest of the batch, on 24 July 2026.
Released packages
- package
robocorp3.1.2 (meta package) - package
robocorp-log3.1.3 - package
robocorp-workitems1.5.1 - package
robocorp-vault1.4.1 - package
robocorp-storage1.1.1 - package
robocorp-windows1.1.2