---
title: "Changelog"
description: "A log of all notable changes to Activepieces"
icon: "code-commit"
---

<Update label="April 2026" description="Network Security">

### Network Security

Activepieces now ships with a built-in **network proxy that protects your automations from network attacks**.

- **One switch to turn it on** — set `AP_NETWORK_MODE=STRICT` and the protection is active. It's **opt-in today**, but in an upcoming release it will become **opt-out** (on by default).
- **Allow list for trusted internal services** — if a flow legitimately needs to reach an internal API or database, add its address (or a whole subnet like `10.10.0.0/24`) to `AP_SSRF_ALLOW_LIST`.
- **Works with your corporate proxy** — if you already use `HTTP_PROXY` / `HTTPS_PROXY`, Activepieces respects them automatically.

See the [Network Security](/install/architecture/network-security) architecture page for the full breakdown.

</Update>

<Update label="April 2026" description="Shared Concurrency Pools">

### Shared concurrency pools

Projects can now share a single concurrency limit through **concurrency pools**, giving platform operators finer control over how worker capacity is distributed.

- **Per-project concurrency** — set **Max Concurrent Jobs** directly in Project Settings > General.
- **Shared pools** — multiple projects can be grouped into the same pool so they draw from one shared limit instead of each having its own.
- **Embedding support** — when provisioning users via JWT, include `concurrencyPoolKey` and `concurrencyPoolLimit` claims to create or reuse a pool automatically. See [Provision Users](/embedding/provision-users).

![Project Settings — Max Concurrent Jobs](/resources/screenshots/manage-concurrency.png)

Learn more in the [Manage Concurrency](/admin-guide/guides/manage-concurrency) guide.

</Update>

<Update label="March 2026" description="Stability & Reliability Improvements">

### Stability & reliability improvements

Major investments in worker architecture, testing, and resilience to ensure more reliable flow execution.

**Worker Architecture**
- Complete worker rewrite (worker v2) focused on stability and reliability
- New sandbox process model with improved error handling and resource cleanup

**Testing & Quality — what we added and why it matters**

Race condition tests:
- **Queue dispatcher** (12 tests) — tests orphaned job handling when a job is dequeued but all waiters have timed out, prevents double-loop spawn during close with in-flight dequeue, verifies single dequeue concurrency control, tests waiter timeout and retry behavior
- **Subflow resume** (8 tests) — tests the race condition where the engine writes pause metadata to Redis before it's persisted to DB, verifies Redis fallback when DB is stale, simulates concurrent reads/writes with spy mocks, covers sync endpoint with concurrent Redis updates
- **Rate limiter** (5+ tests) — tests concurrent job slot allocation, idempotency with concurrent dispatch, per-project isolation so different projects don't interfere
- **Concurrent flow execution** — end-to-end test creating 5 concurrent flow runs verifying none get stuck or deadlocked
- **Memory lock** — verifies mutual exclusion (two concurrent lock acquire calls on same key are serialized)

Worker unit tests:
- **Worker polling** — tests job execution lifecycle, resilience to invalid job data, null polls, unrecognized job types, mixed valid/invalid sequences
- **Sandbox execution** — tests sandbox creation, startup, RPC communication, stdout/stderr accumulation, resource cleanup on timeout or memory issues, process cleanup and listener removal
- **Process forking** — tests execArgv configuration (memory limits, node options), environment variable propagation
- **Cache logic** — tests cache hit/miss, disk persistence, memory caching, cache invalidation predicates
- **Configuration** — tests config loading for different container types (WORKER_AND_APP vs WORKER)

End-to-end validation:
- **[Smoke tests](https://github.com/activepieces/activepieces/blob/main/.github/workflows/smoke-test.yml) in GitHub Actions** — validates health checks and webhook flow execution on AMD64 and ARM64
- **[Benchmark tests](https://github.com/activepieces/activepieces/blob/main/.github/workflows/benchmark.yml) in GitHub Actions** — load testing across 6 app/worker configurations measuring throughput, mean latency, P50, P99 ([see results](/install/architecture/benchmark))

**Resilience**
- Worker gracefully handles invalid job data, null polls, and unrecognized job types
- Sandbox properly cleans up processes, listeners, and resources on timeout or memory issues
- Race condition fixes for subflow resume and user interaction jobs

</Update>

<Update label="March 2026" description="Platform Admin">

### Platform Admin — full UI redesign

A comprehensive visual refresh across all Platform Admin and Project pages with a cleaner, more consistent interface.

**Platform Admin**

- **Projects** — filter chips, inline edit icons, and cleaner sidebar without branding
- **Users** — new Role and Last Active columns, dedicated Invite button, and per-row action menus
- **Project Roles** — switched from table to card-based layout with permission viewing
- **Audit Logs** — fully enabled with Action, Performed By, Project, and Date Range filters, plus detail slide-over panels with a full JSON payload viewer
- **Secret Managers** — card-based layout with Hashicorp Vault, AWS Secrets Manager, Cyberark Conjur, and 1Password
- **Branding** — refreshed page layout

**Project pages**

- **Automations** — renamed from "Flows", with Type and Owner filters, search, step icon details, status toggles, and favorites
- **Connections** — Pieces and Owner filters, flow usage count, inline edit and refresh actions
- **Runs** — updated tab navigation and consistent styling

**General improvements**

- Unified tab navigation across Automations, Runs, and Connections
- Platform Admin link added to the bottom of the project sidebar
- Slide-over panels for detail views instead of full-page navigation
- Previous / Next pagination style throughout
- Sidebar header replaced with a "Back to app" link

</Update>

<Update label="March 2026" description="Staging Environment & Release Process">

### Dedicated staging environment & improved release process

All changes now go through a dedicated staging environment before reaching production. Every update is validated internally for a minimum of 16 hours before being promoted, ensuring higher reliability and fewer disruptions for our users.

- **Staging-first deployment** — every change is tested in a production-like environment before going live
- **Daily production promotions** — only validated, stable builds are promoted to production
- **Weekly self-hosted releases** — predictable, stable releases published every week for self-hosted customers
- **Emergency hotfix path** — critical fixes can still be fast-tracked to production when needed

[Read more about our release cycle](/handbook/engineering/onboarding/release-cycle)

</Update>

For previous releases, see the [GitHub Releases](https://github.com/activepieces/activepieces/releases) page.
