Closed-app backup expectations
Understand when automatic backups can run with Paydae open or closed.
Only while Paydae is open4 sections
Automatic execution depends on the selected mode. The current selection and the mode supported by the device are shown separately in Workspace Backup; do not read a selected option as proof that a backup already ran.
Only while Paydae is open
This is the normal app-open boundary. Paydae can run a due schedule while the desktop is open. If the preferred time passed while the app was unavailable, the scheduler can catch up after startup. Check Last automation run and Last backed up rather than relying on the schedule alone.
Even when Paydae is closed
Selecting Even when Paydae is closed allows an owned Windows Task Scheduler task to start the short-lived backup runner. The helper text in the UI is Closed-app backups use the Windows background task runner on this device. The setting must be saved, the Windows user who configured it must remain signed in, the device must be connected to AC power, and the destination and protected smart password must be available. The task uses Windows’ defaults to prevent starting on battery and to stop if the device switches to battery power. Paydae does not install an always-running service.
What to check
At Workspace Backup, review Requested execution mode and Effective execution capability, along with Catch-up due/Next automatic backup and Last automation run. Automatic backup can show Off, Ready, Due, Snoozed, Running, Failed, Needs password, or Unavailable. The separate scheduler status can show Disabled, Enabled, Active, Needs repair, Failed, or Unavailable. A saved request for closed-app backups does not mean the task is currently active: until registration is confirmed, the effective capability is app-open-only. If settings are saved but registration fails, the screen reports that partial result and retains the repair details. Corrupt scheduler, settings, or other local backup state can also show an execution-attention message with a repair reason. Select Repair closed-app backups when offered and review the reason; a selected mode or an Enabled status alone does not confirm that a backup succeeded.
If Workspace Backup reports Needs repair, select Repair closed-app backups and check that the effective capability becomes available. The app checks the task’s effective runner, account, schedule, and settings; a task simply existing in Windows does not prove it can run.
If a settings revision conflict appears, another request saved newer settings first. The screen refreshes those saved values and rebases your unsaved edits. Review the current settings and save again; the conflicted request was not applied.
Important boundary
Closed-app execution is a local Windows task, not a cloud backup. It uses the protected smart password and local destination configured for this Windows user. If Task Scheduler is unavailable, registration fails, saved backup state needs repair, the destination cannot be written, or the secret cannot be read, closed-app execution may stop or fall back to app-open-only. Create backup now remains the manual fallback. Configure and repair the task from the normal signed-in Windows account that owns the workspace.
After an application upgrade, repair the task from Workspace Backup if closed-app capability needs attention. Repair uses the runner installed with the current app and updates the owned task; do not reuse or manually restore an old runner path.
During a normal uninstall, Paydae removes only the closed-app backup tasks owned by the current Windows user and this installation. An upgrade preserves the task; check its capability afterward and use the in-app repair control if needed.