n8n 2.27.0 - Execution Index Added; Expect Short, Online Migration

What changed

n8n 2.27.0 ships a targeted database migration that creates an index on the execution_entity table. For large instances that table can be substantial, so the migration may take several minutes to complete; importantly the maintainers note the database remains available while the change runs. The release also contains bug fixes such as making conditional credential fields optional rather than forbidden and API-related corrections.

Why it matters for businesses

An index on execution_entity addresses a common scalability bottleneck for workflow platforms: slow queries when scanning historical or in-flight executions. Faster lookups reduce UI latency, reporting delays, and can lower load on database replicas. Because the migration is online, organizations avoid a hard outage, but the temporary increased I/O and locks can still affect performance on heavily loaded systems during the change window.

Recommended actions for leaders

Treat this as a routine but non-trivial infrastructure change. Schedule the upgrade during a low-traffic period, ensure recent backups, and verify resource headroom (CPU, I/O) on database hosts. Run the migration first in staging against a production-sized dataset to gauge duration. Update runbooks and monitoring to catch transient impacts and validate key workflows post-migration. Finally, coordinate with teams that depend on long-running executions or reporting to manage expectations during the index build.