Errors
Error -5009: the number is undocumented. The provider is diagnosable.
By the Noah team·Updated September 20, 2026·4 min read
Short answer-5009 has no documented meaning. Apple publishes meanings only for the low FileProvider numbers; -5009 is provider-defined and no provider has published it, so any page that tells you what it means is guessing. Skip the number. Confirm the failure matches (a cloud file operation failing under the NSFileProviderErrorDomain name), find which provider owns the failing files, and check that provider's sign-in, storage, and connection.
The dialog reads NSFileProviderErrorDomain error -5009 and offers nothing else. The natural next step — searching the code — finds one August 2026 thread guessing an iCloud outage, unconfirmed.
That guess is all anyone has published. The honest version: the number identifies nothing on its own. What identifies the problem is everything around it — which app was syncing, which files, and whether that provider's basics check out. This page walks that instead of the number.
What -5009 is known to be
Almost nothing, and that is the point. Apple's published FileProvider error list covers the low numbers — sign-in, quota, unreachable server, missing item. -5009 is outside that list: a provider-defined code no provider has defined in public. The single public thread, from August 2026, suspected an iCloud outage and never confirmed it.
Treat any stronger statement with suspicion, including future ones. A cause for -5009 becomes real when a provider documents it, or when the same failure reproduces against a known state — not when a thread upvotes it.
What Noah can determine on this Mac
NoahNoah can read a ranked list of the five processes — the programs your Mac is running — that are using the most processor. That shows whether fileproviderd or a provider's app is working hard during the failure. Noah can read the recent unified log, where FileProvider entries can name the provider that failed and the operation it was attempting. And Noah can list which cloud apps are installed, matching the failing folder to its owner.
What Noah cannot do is look up -5009 — there is nothing published to look up — or reach the provider's servers. Noah narrows the failure to a provider and an operation; the provider's status page covers the rest.
Steps to leave for last
Do not unlink the account or reinstall the provider to clear an undocumented number. Both can force large parts of the library to sync again on the hope that the number meant corruption, and neither is indicated when the cause is unknown.
Fixwrite down the exact dialog text, the provider, and the time before you change anything. If the failure clears on its own — outages do — that record is what tells you it was never local. If it persists, it is what support asks for first.
Frequently asked questions
What does NSFileProviderErrorDomain error -5009 mean?
Nothing published. Apple documents only the low FileProvider codes; -5009 is provider-defined and no provider has defined it publicly. Diagnose the provider and the failing operation instead of the number.
Was the August 2026 -5009 an iCloud outage?
Unconfirmed. One thread suspected it and never verified. Check the provider's status page for your own failure rather than relying on that guess.
Should I delete files to fix -5009?
No — not to clear the number. If one file fails while the rest sync, that item is suspect; otherwise leave the library alone until the provider checks out.
Commands in this guide are standard, read-only macOS diagnostics unless noted; anything that changes your system is called out. When in doubt, back up first with Time Machine.