Temporal opens standalone activities to everyone as n8n grinds through reliability fixes

Temporal turns Standalone Activities on by default

The headline of the week belongs to Temporal Server, which promoted Standalone Activities and start delay to general availability, flipping activity.enableStandalone and activity.startDelayEnabled on by default. That means activities no longer have to be bolted to a workflow to exist: they can be scheduled on their own, and they can be told to wait before starting. Alongside the GA flip, the release adds operator APIs for the humans and services running those activities — pausing and resuming an in-flight activity, resetting its attempt state (with optional heartbeat cleanup or restoration of the original options), and updating or reverting selected options. Operators are opt-in behind history.enableStandaloneActivityOperatorCommands, so existing deployments won't find new commands in their history service until they ask for them. Batch operations round out the release, giving operators a way to act on many activities at once rather than one at a time. For teams that have been using standalone activities in preview, this is the release that removes the feature flags; for everyone else, it's a new primitive to design around.

n8n's week: keeping jobs honest when things go wrong

n8n shipped a dozen releases across four version lines, and the through-line is failure handling — what the platform does when a job, a secret provider, or a runner goes sideways. Running jobs now get cleaned up when a workflow run rejects, so a crashed execution no longer leaves debris behind, and a job whose key has vanished from the store still reports its original error instead of a misleading one — a small change that matters a great deal when you're reading logs at 3am. Task runner timeouts are now capped to the graceful shutdown window, so a long-running task can't outlive the shutdown it's supposed to cooperate with. And when a replacement external secrets provider fails to come up, n8n keeps the currently serving provider active rather than leaving workflows without secrets, with the same safeguard landing on the 2.38 line.

Performance and data integrity

Two fixes target performance rather than correctness. Source control pushes now bound their peak memory instead of ballooning on large pushes, and pairedItem ancestry traversal is memoized, cutting repeated work on expressions that walk item lineage. On the data side, n8n repairs legacy-format data-encryption keys during bootstrap, a fix aimed at instances that have carried old key formats forward through upgrades. Source control over HTTPS also got more forgiving: n8n now trusts the CA named in GIT_SSL_CAINFO for remote repositories, which unblocks self-hosted Git servers behind private certificate authorities.

Security, sandboxing, and the rest

The sandbox npm install flags are now selected by provider, tightening how dependencies are fetched inside the sandbox. MCP toolkit members execute on workers as they should, rather than wherever they happened to land. Two releases reuse an existing consent grant when a visitor authenticates mid-flow instead of asking again — the same fix appears on both the 2.38 and 2.39 lines. The 2.38.0 and 2.39.0 releases carry the broader fix set for this stretch, including parameter binding for MongoDB sort and projection and an AMQP trigger that reattaches its receiver link when the broker detaches it. The 1.123 line got a maintenance-only bump with no user-facing changes worth naming.