Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A launchd backup can run successfully in Terminal and still fail every scheduled run. The usual causes are that macOS privacy controls (TCC) deny the process access to the protected Documents folder, or that the job is a system LaunchDaemon running as a different user with a different home directory. A three-week gap is usually an observability problem as well: without persistent standard output, error logs, exit-status checks, and missed-run alerts, launchd can keep starting a job whose backup command is failing.
Fix the problem by identifying the job context, replacing ~ with an absolute path, authorizing the executable that actually opens the files, validating the plist and its permissions, and adding a health check that proves a recent backup artifact exists.
As an Amazon Associate I earn from qualifying purchases.
What does launchd do, and why can the same command behave differently?
launchd is macOS’s scheduler and process manager. launchctl loads, unloads, inspects, and reports on those jobs. Apple documents per-user jobs in ~/Library/LaunchAgents and system jobs in /Library/LaunchDaemons and related system locations. The scheduler does not recreate your interactive Terminal session when it starts a process.
A Terminal command inherits your logged-in user, shell startup files, PATH, home directory, current directory, keychain access, and graphical session. A launchd job receives only the environment and credentials defined by its launch context and plist. That can change the executable found, the value of $HOME, the destination resolved from ~, available credentials, and the privacy identity macOS evaluates.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Apple Support describes launchd as the process used to manage daemons and agents and to run shell scripts. Treat the plist as a separate execution environment, not as a delayed copy of your Terminal command.
Is this a LaunchAgent or a LaunchDaemon?
A backup of one user’s Documents folder normally belongs in that user’s context. A LaunchAgent runs for a logged-in user; a LaunchDaemon runs in system context and does not know which users are logged in. The distinction affects the effective UID, $HOME, credentials, GUI availability, and the TCC decision that applies.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Characteristic | LaunchAgent | LaunchDaemon |
|---|---|---|
| Typical plist location | ~/Library/LaunchAgents |
/Library/LaunchDaemons or another system launchd directory |
| Execution identity | The logged-in user | Usually a system account, often root, according to the plist and launchd domain |
| Home directory | The user’s home, such as /Users/alice |
Not the logged-in user’s home unless explicitly designed that way |
| Desktop and GUI access | Available only within the user’s session and subject to session state | Generally unavailable |
| Best fit for a personal Documents backup | Usually the simpler design | Only when a privileged helper intentionally mediates access |
Inspect the loaded domain rather than guessing from the filename. For a user job, run launchctl print gui/$(id -u)/com.example.backup; for a system job, use launchctl print system/com.example.backup, replacing the label with the plist’s Label. Put temporary diagnostics in the script itself:
id
whoami
printf 'HOME=%sn' "$HOME"
printf 'PWD=%sn' "$PWD"
If a job intended for Alice reports a system account or a home directory such as /var/root, fix the context before troubleshooting the backup application. Running it as root is not a substitute for a user-context design.
Why does macOS block access to Documents?
macOS privacy protections cover Documents, Desktop, Downloads, iCloud Drive, and other sensitive locations. The Transparency, Consent, and Control (TCC) system records a user’s decision for the process requesting access. Apple notes that broad backup workflows may need Full Disk Access because a backup must read files wherever they reside. A plist, shell script, or code-signing entitlement cannot silently grant that user permission.
Rank #2
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Open System Settings > Privacy & Security > Full Disk Access and add the application or executable that performs the file operation. Depending on the workflow, the relevant entry may be a signed backup app, its helper, a shell interpreter, or a wrapper you wrote. The scheduler itself is not the backup reader; granting access to an unrelated launcher will not repair the process that opens files.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsApple Developer documentation states: “Certain app workflows, like an app for backing up your Mac, require access to files wherever they reside on a file system.” The practical implication is that authorization must be granted by a logged-in user and can change when the executable, signature, path, or helper architecture changes.
How do I diagnose a backup that works in Terminal but fails in launchd?
1. Identify the loaded job and its effective user
Read the plist’s Label, then inspect the matching launchd domain with launchctl print. Confirm the user, group, home directory, and destination from inside the job. A backup targeting /Users/alice/Documents should not rely on whichever account launchd happens to choose.
Also check whether the plist is actually loaded. launchctl list | grep com.example.backup can show a label and recent status for a user-domain job; use the appropriate domain when inspecting a system job. A missing label means the schedule was never loaded, while a loaded label with a nonzero last status points to a failed run.
2. Replace tilde expansion with an absolute path
Do not use ~/Documents in a plist argument or in a script that might run outside your login shell. Use an explicit path such as /Users/alice/Documents, and log both that destination and the value of $HOME. Tilde expansion is performed by a shell, not by launchd itself, and a daemon may have no relationship to the home directory you expected.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
3. Trace the complete executable chain
Write down every process involved: the plist’s Program or first ProgramArguments item, any shell wrapper, and the backup binary. Then determine which process actually opens the Documents files. Grant privacy access to that process in Full Disk Access or the relevant Files and Folders pane. If the plist launches /bin/sh, which then starts a backup binary, authorizing a different terminal application may have no effect.
An Apple Developer forum report describes this exact pattern: a program launched by launchd received Operation not permitted for Desktop or Documents while the same program run in the foreground worked. It is a useful diagnostic example, not a universal command recipe. Moving operational files out of protected folders can alter the result, but it does not prove that the original authorization problem was solved.
4. Validate the plist and filesystem permissions
Check the spelling and order of ProgramArguments, the executable’s absolute path, the StartCalendarInterval schedule, and every log destination. A malformed argument can make a job appear to start while the backup command exits immediately.
For globally installed daemons, Apple requires the plist and containing directories to be owned by root and not writable by group or other users. Verify ownership and modes before changing them. A backup vendor’s helper documentation gives a concrete example in which incorrect ownership or permissions on /Library/LaunchDaemons prevented helper installation without a useful notification; that vendor’s repair sets the directory to mode 755 and owner root:wheel. Do not apply that repair blindly to unrelated paths: inspect the actual file and directory first.
5. Capture durable output and exit status
Set StandardOutPath and StandardErrorPath to writable locations that survive logout and reboot. Avoid a destination inside the protected folder you are debugging. The wrapper should record the start time, effective UID, $HOME, resolved source and destination, and the backup command’s exit status.
Rank #4
- Plug-and-play expandability
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
#!/bin/sh
LOG=/var/log/example-backup.log
{
printf 'nSTART %sn' "$(date -u)"
id
printf 'HOME=%sn' "$HOME"
printf 'SOURCE=%sn' '/Users/alice/Documents'
/usr/local/bin/backup-tool --source '/Users/alice/Documents' --destination '/Volumes/Backup/Documents'
status=$?
printf 'EXIT_STATUS=%sn' "$status"
exit "$status"
} >>"$LOG" 2>&1
Use the real backup executable and destination in place of the example. Returning the backup command’s status is important: if the wrapper always exits zero, launchd and your monitoring system will treat a failed copy as a successful run.
6. Use a minimal, explicit plist
A user LaunchAgent might look like this:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE plist PUBLIC '-//Apple//DTD PLIST 1.0//EN' 'http://www.apple.com/DTDs/PropertyList-1.0.dtd'>
<plist version='1.0'>
<dict>
<key>Label</key>
<string>com.example.backup</string>
<key>ProgramArguments</key>
<array>
<string>/Users/alice/bin/backup-wrapper.sh</string>
</array>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key><integer>2</integer>
<key>Minute</key><integer>0</integer>
</dict>
<key>StandardOutPath</key>
<string>/Users/alice/Library/Logs/example-backup.out</string>
<key>StandardErrorPath</key>
<string>/Users/alice/Library/Logs/example-backup.err</string>
</dict>
</plist>
Use a path and label that belong to your account. After editing, load the job in the correct GUI domain with launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.example.backup.plist. If it is already loaded, remove it from that domain first with launchctl bootout gui/$(id -u)/com.example.backup, then bootstrap the revised file. Inspect it again with launchctl print gui/$(id -u)/com.example.backup and run the wrapper directly once to separate script errors from scheduling errors.
7. Check launch constraints and unified logs
Calendar scheduling is only one condition. Newer macOS releases can apply launch-environment constraints that prevent a binary from launching when the plist’s requirements are not met. Inspect the job status and unified logs in Console or with the log utility before disabling security controls or changing backup data. Look for denied file access, missing executables, malformed plists, and nonzero exits at the scheduled time.
Free tools Windows power users keep installed
One-click scans. No signup required.
How do I prove that the fix has held?
A successful schedule is not proof of a successful backup. Run the job once interactively through the same wrapper, then trigger it from launchd and compare the two log entries. Confirm that the logged UID, home directory, source path, destination, and exit status are the values you expect.
Add an independent health check that examines the backup destination for a newly updated artifact, manifest, or snapshot marker. Alert when its age exceeds the intended interval plus a reasonable grace period. The checker should report a stale artifact even if launchd still shows the job as loaded; this is what turns a multi-week silent gap into a same-day incident.
Best Value
- 【Versatile Storage Expansion – For Gaming, Work & Everyday Use】 Running out of space on your PS5 or Xbox Series X/S? This external hard drive lets you store and play PS4 / Xbox One games directly, instantly freeing up your console’s internal storage for next‑gen titles. At the same time, it handles work file backups, media libraries, and cross‑device data transfers with ease. One drive, all your needs. *（Note: PS5 / Xbox Series X|S games cannot be run or stored directly from the external hard drive. However, by offloading your PS4 / Xbox One games, you can free up valuable space for newer titles.）*
- 【Patented Silicone Sleeve – Data Protection You Can Count On】 Worried about drops? We’ve got you covered. The patented built‑in silicone sleeve acts like a shock‑absorbing armor, cushioning your drive against bumps and falls. Whether it’s important work documents, precious family photos, or hard‑earned game saves, your data deserves this level of protection.
- 【Plug & Play, Compatible with Computers & Consoles】 No complicated setup—just plug in and go. Works seamlessly with Windows, Mac, and Linux computers, as well as PS4, PS5, Xbox One, and Xbox Series X/S. Process files at the office, back up data at home, or enjoy gaming in your downtime—one drive handles all your devices, simply and hassle‑free.
- 【USB 3.0 Ultra‑Fast Transfer – No More Waiting】 Tired of watching progress bars crawl? With USB 3.0 speeds up to 5Gbps, large files transfer in seconds. Whether you’re moving work documents, transferring hundreds of gigs of games, or backing up a year’s worth of photos, you get more done in less time.
- 【Sleek, Lightweight, and Ready to Go】 Weighing just 0.16 kg—lighter than a can of soda—this compact drive features a stylish mirror‑and‑frosted finish. Toss it in your bag and go, whether you’re heading to the office, visiting a friend for a gaming session, or giving a presentation on the road.
- Verify the expected artifact exists and has a recent modification time.
- Record nonzero exit statuses and preserve the associated stderr.
- Test after logout, reboot, and a normal sleep/wake cycle.
- Perform a restore of a representative file, not only a listing of backup metadata.
What should I avoid while repairing the job?
- Do not grant permission to launchd itself and assume the data reader is covered. Authorize the executable that opens the protected files.
- Do not switch to root merely because a daemon failed. Root changes the home directory and credentials and does not automatically bypass TCC.
- Do not hide errors by redirecting output to
/dev/null. Keep persistent stdout and stderr until the job has been reliable for several cycles. - Do not move Documents permanently just to evade privacy controls. That may change the symptom while creating a weaker privacy design.
- Do not copy a permission repair from another Mac. Check the actual owner, mode, installation method, and macOS release first.
How should I evaluate a different backup application after fixing launchd?
Hardware capacity does not solve a TCC denial. If you replace the script or scheduler, evaluate the software’s signed app and helper architecture, whether macOS can authorize the component that reads protected files, and whether the product reports missed runs instead of only successful launches.
| Evaluation question | Why it matters |
|---|---|
| Which signed component performs the file reads? | That is the component whose privacy authorization must remain valid after updates. |
| Are missed runs and failed transfers reported? | Alerting prevents a stale backup from looking healthy for weeks. |
| Does it support the macOS release you run? | Launch constraints and privacy behavior can change between releases. |
| Can you verify and restore files? | A completed copy is not evidence that the data is recoverable. |
| How are destinations encrypted and retained? | Confidentiality and recovery history matter as much as copy speed. |
What is the practical diagnosis?
When Terminal succeeds but launchd fails, treat it as a context-and-privacy mismatch first, not as proof that the backup data is corrupt. Identify the launch domain, log the effective identity and absolute paths, authorize the real file-reading executable, validate the plist and its installation permissions, and monitor the age of a real backup artifact. Those controls address both halves of the incident: the immediate Operation not permitted error and the missing evidence that allowed failures to continue unnoticed.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteFrequently Asked Questions
Will rebooting my Mac reset the Documents permission?
No. TCC decisions normally persist across reboots. You may need to reauthorize after replacing, moving, re-signing, or substantially updating the executable that performs the backup.
Can a shell script itself receive Full Disk Access?
System Settings may list the interpreter, wrapper, app, or helper rather than the script file. Authorize the executable that actually opens the protected files, and verify the complete chain when a wrapper starts another binary.
Should the backup run while no user is logged in?
A user LaunchAgent depends on that user’s session, while a LaunchDaemon is designed for system context. If unattended operation is required, use a deliberately designed helper and confirm how it obtains the intended user’s data and privacy authorization.
How often should a stale-backup alert fire?
Set the threshold to the planned schedule interval plus a grace period for sleep, network availability, and transfer time. The exact threshold depends on your schedule; the essential rule is that it must be shorter than the maximum outage you can tolerate.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
