Always-on automation

Okinawa now supports automations for building always-on agents that run based on triggers and instructions you define. Unlike manual workflows, automations run continuously in the background and respond to events as they happen.

Automations are powered by the same agent architecture as interactive workflows, but they run autonomously — spinning up cloud sandboxes, following your instructions, and delivering results without any manual intervention.

Trigger types

Automations can be triggered by a variety of events:

• Scheduled — Run on a cron schedule (every 5 minutes, hourly, daily, weekly, or custom)
• Slack — Respond to messages, reactions, or channel activity
• GitHub — Trigger on pull requests, pushes, issues, or deployments
• Linear — React to ticket creation, status changes, or comments
• PagerDuty — Automatically respond to incidents and escalations
• Webhooks — Accept custom HTTP payloads from any service

Memory and learning

Agents have access to a memory tool that lets them learn from past runs and improve with repetition. Over time, your automations become more efficient at handling edge cases, routing tasks, and making decisions based on historical patterns.

Templates and marketplace

Get started quickly with pre-built automation templates at okinawa.com/automations. Choose from categories like DevOps, customer support, data pipelines, and security operations. You can also publish your own automations to the marketplace for others to use.

Speed and reliability

We've made significant performance improvements across the entire platform. These changes affect every workflow, every trigger, and every integration — delivering a noticeably faster and more reliable experience.

Our engineering team spent the last sprint optimizing the core execution engine, reducing overhead in the scheduling system, and improving how we handle concurrent workflow runs.

By the numbers

• 40% faster workflow execution times across all plan types
• 60% reduction in API latency for real-time triggers
• 99.99% uptime for the last 30 days — our best stretch ever
• 3x improvement in memory usage for large workflow runs
• 50% faster cold start times for cloud agent sandboxes

Improved error handling

We've overhauled the error recovery and retry logic. Workflows that encounter transient failures (network timeouts, rate limits, temporary service outages) now recover automatically with exponential backoff and smart retry strategies.

You can also configure custom retry policies per step — setting max attempts, delay intervals, and fallback actions when retries are exhausted.

What's next

These improvements are available to all users immediately — no configuration changes needed. We're continuing to invest in performance and will share more updates in the coming weeks. Check our status page for real-time performance metrics.

Deprecation timeline

API v2 will be officially deprecated on May 1, 2026. After this date, all v2 endpoints will return a 410 Gone response. We encourage all users to migrate to API v3 as soon as possible to avoid any disruption to your workflows.

API v2 was introduced in 2024 and has served us well, but v3 brings significant improvements in performance, security, and developer experience that require breaking changes.

What's changing in API v3

• Authentication — New OAuth 2.0 flow with refresh tokens and scoped permissions. API keys are no longer supported.
• Rate limits — Updated to 1,000 requests/min (up from 100), with burst allowance up to 2,000 requests/min for short periods.
• Webhooks — Signature verification is now required on all incoming webhook payloads using HMAC-SHA256.
• Removed endpoints — Several deprecated endpoints have been removed. See the full list in the migration guide.
• Response format — All responses now use a consistent envelope format with data, meta, and errors fields.

Migration guide

We've published a comprehensive migration guide at docs.okinawa.com/api/v3/migration that covers every change in detail. The guide includes:

• Side-by-side comparisons of v2 and v3 requests
• Automated migration scripts for common SDKs
• A compatibility layer you can enable during the transition
• FAQ and troubleshooting for common migration issues

Support

If you need help migrating, our developer relations team is available on Discord and via email at api-support@okinawa.com. We also offer free migration consultations for teams with more than 50 active workflows.