The Backstage project released version 1.55 of its open-source developer portal framework, introducing automatic recovery for Software Template tasks that crash or time out. The update also removes deprecated catalog APIs and shifts the search module to Elasticsearch 8, creating several breaking changes platform teams must navigate during upgrades. The feature addresses a long-standing user request for resilience when scaffolder processes fail mid-execution.

Task recovery operates through a new scaffolder.taskRecovery configuration section. When activated, the scaffolder restarts a task from its last finished step, retains task secrets until the task hits a terminal state, and saves completed step outputs for later steps to access. The release notes caution that actions in recovered tasks should be idempotent or employ checkpoints, since a restarted task may execute an action twice. The new section replaces three experimental flags, which continue functioning as fallbacks. Workspace serialisation is optional and requires a separate provider module—the new database provider caps storage at 50 MB for development use, while production installations are directed toward the GCP module or comparable external stores. Core plugins including the catalog, search, and TechDocs now load pages only when rendered, shrinking the initial app bundle.

In April 2025, on a GitHub issue tracking scaffolder task retries, Manoj Azad noted that "having to re-run the entire scaffolder process can be not only inconvenient but also problematic from a technical standpoint." The 1.55 feature covers tasks interrupted by crashes or time-outs, addressing part of that concern. The catalog backend drops the catalog.enableRelationsCompatibility option, meaning entity relations now return only targetRef, and removes the deprecated CodeOwnersProcessor and AnnotateScmSlugEntityProcessor in favor of community modules. The Elasticsearch module now demands version 8.19 or later, though AWS and OpenSearch providers remain unaffected. Michael Todorovic, a senior SRE at Veepee, changed the GitLab merge request and push actions to compare files locally, cutting API requests for a repository of several hundred files from roughly 300 to under ten—a step that took 5 to 15 seconds now completes in about 3 seconds.

Several changes target governance and speed. The scaffolder.requireScmUserCredentials option, first added in patch 1.54.6, mandates user-provided credentials for supported GitHub, GitLab, Bitbucket, and Azure DevOps actions. Permission policies that deny unknown permissions must now explicitly allow scaffolder.template.dry-run to preserve template dry runs. TechDocs strips MkDocs plugins absent from a built-in allowlist, requiring teams that need extra plugins to list them under techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins. Since 15 September, maintainers have shipped three patch releases—version 1.55.1 fixed the new backstage-cli pm verify-patches command and TechDocs add-ons on the new frontend system, while 1.55.2 and 1.55.3 corrected how TechDocs handles MkDocs Markdown extension configuration. The release also documents security fixes in seven packages, including the OIDC and Cloudflare Access auth providers and the proxy backend, with the Cloudflare Access provider now requiring the application audience in its configuration. The next minor version, 1.56.0-next.2, was published on 6 October. Platform teams navigating the transition will need to weigh the operational resilience gains from task recovery against the engineering hours required to refactor deprecated APIs and update Elasticsearch dependencies. Organizations that rely heavily on scaffolder workflows stand to benefit most, though the governance tightening around credentials and permissions signals a maturation phase that may complicate existing pipelines before it simplifies them.