One of the biggest headaches in automation is handling duplicate triggers. The new @runtime.idempotent decorator uses a lightweight, pluggable storage backend (Redis, SQLite, or in-memory) to ensure that even if your webhook fires twice, your critical routine runs exactly once. This is a game-changer for financial and inventory automations.
The AIO product team has already published a roadmap preview for 2026: aio runtimes 2.5.0
Here is a breakdown of the headlining features: One of the biggest headaches in automation is
We ran three standard automation workloads on identical hardware (Windows 11, 16GB RAM, Intel i7-1260P) to compare performance. Here is a breakdown of the headlining features:
| Workload | v2.4.3 Execution Time | v2.5.0 Execution Time | Improvement | | :--- | :--- | :--- | :--- | | SAP GUI Data Entry (1k rows) | 14m 22s | 11m 07s | 22.5% faster | | Web Scraping (10k products) | 8m 45s | 6m 12s | 28.9% faster | | PDF Invoice Parsing (500 docs) | 31m 18s | 24m 55s | 20.3% faster | | Memory Footprint (idle bot) | 892 MB | 612 MB | 31.4% reduction |
Verdict: If you are running high-volume automations, the upgrade to 2.5.0 will pay for itself within weeks via reduced compute time alone.
"It worked on my machine" is no longer acceptable. AIO Runtimes 2.5.0 natively supports OpenTelemetry (OTLP) gRPC export. You can now stream traces, metrics, and logs directly to Prometheus, Jaeger, or any OpenTelemetry-compatible collector without third-party SDKs cluttering your runtime.