Moltaro 0.0.57-beta
Release date: 2026-09-10
File Protection can reconnect an agent to its existing record, preserving its sources and history, and makes monitoring setup and retained-copy status clearer. Background functions use bounded execution with prompt wake-up, while managed deployments remove obsolete local installation packages immediately to recover disk space for operations such as backups.
Highlights
Section titled “Highlights”- Reconnect a File Protection agent after local state is lost without creating a replacement record or reassigning its sources.
- Enable baseline monitoring for newly created sources and agents, preview the eligible notification audience, and preserve navigation across reloads.
- Keep queued background execution bounded and wake available execution slots promptly when work arrives.
- Retire excess local release packages after successful deployment without the former fourteen-day delay, preserving current and previous artifacts.
Detailed changes
Section titled “Detailed changes”File Protection connection and monitoring
Section titled “File Protection connection and monitoring”An authorized operator can issue a one-time reconnect code for an existing agent. The guided command reconnects that same identity and keeps source assignments, stored versions, policies and history. Reconnection replaces the old credential and rejects late requests from the old connection. A revoked agent cannot be revived this way. Work already accepted for server finalization can complete; other interrupted transfers remain subject to their normal retry and expiry rules.
New sources start with baseline failure, progress, schedule and recovery monitoring; new agents start with availability monitoring. File freshness remains disabled until an operator chooses its interval. Existing policy settings, including deliberately disabled rules, are preserved. Enabling a policy does not automatically select administrators as recipients.
Notification recipients are configured in a compact two-step wizard using roles and responsibility groups. Its preview counts distinct eligible recipients using the same permission rules as delivery. Source and agent navigation follows the URL, so Back, Forward, reload and refresh retain the selected context. Status displays distinguish a failed recent run from previously available stored copies.
Background functions and dashboards
Section titled “Background functions and dashboards”Each Worker host limits simultaneously executing queued functions instead of claiming a batch ahead of available execution slots. Work can wake idle slots immediately, and available queued work continues without an extra polling delay between batches. An unexpected cancellation within one execution does not permanently remove its execution slot.
Embedded dashboards no longer show a host-level refresh action they cannot handle. Their own refresh controls remain available; built-in widget dashboards retain their existing refresh behavior.
Managed deployment storage
Section titled “Managed deployment storage”Successful deployments immediately remove known obsolete local runtime and VM agent package copies. Current installations, the previous distinct accepted artifacts, stopped installations and unfinished preparations remain protected. Copies still required by an active process or container cannot be removed. This policy applies to installation caches; backup retention and Object Storage contents are unchanged.
Database and upgrade impact
Section titled “Database and upgrade impact”A Workspace schema upgrade is required for reconnect codes bound to an existing File Protection agent. Existing sources, agent assignments, retained versions, retention policies and business records are preserved. Portal requires no schema change.
Managed Apps receive a full runtime replacement with a brief interruption while their services stop, upgrade and restart. Take the standard database and runtime recovery points before activation. A downgrade must invalidate outstanding reconnect codes before an older runtime can accept enrollment requests. Restoring a database recovery point discards later writes; file bodies referenced by an existing backup still depend on their original Object Storage.
Deployment and operator actions
Section titled “Deployment and operator actions”Deploy using ReplaceRuntime, including the matching Portal, public and agent
documentation, Runtime VM agent bundle and every Managed App runtime. Complete
the compatibility checks for all applications before activation. Deployment
automatically assigns and verifies the VM agent bundle version; no manual agent
version edit is required.
For File Protection reconnection, download the matching agent distribution and follow the reconnect instructions for the existing agent. Reconnection is an explicit operator action and changes credentials; deploying this release alone does not reconnect offline customer agents. Review recipient routing when enabling monitoring on new objects.
Queued function concurrency defaults to two executions per Worker host. The
optional Moltaro:BusinessFunctions:JobWorker:MaxConcurrentJobs setting accepts
1–16 and requires a Worker restart. No override is required for this release.
Compatibility and breaking changes
Section titled “Compatibility and breaking changes”Existing File Protection identities and stored-copy contracts are preserved. Reconnect requires the matching agent CLI and runtime. Enrollment responses add the optional target-agent identity and agent lifecycle version; strict response parsers must tolerate these additive fields. A new recipient-preview endpoint evaluates draft routing without saving it. After an explicit reconnect, clients must use the new credential. Existing retention settings and file deletion rules are unchanged.