If you’ve hit errordomain=nscocoaerrordomain&errormessage=could not find the specified shortcut.&errorcode=4 and immediately assumed it meant some generic system file went missing, you’re not alone — but you’re also probably looking in the wrong place.
In the overwhelming majority of real cases, “shortcut” in this error means exactly what it sounds like: an actual shortcut from Apple’s Shortcuts app, the automation tool, not a system-level file alias. Once you know that, the fix usually takes minutes instead of hours.
What errordomain=nscocoaerrordomain&errormessage=could not find the specified shortcut.&errorcode=4 Is Telling You
NSCocoaErrorDomain is the umbrella category Apple’s Cocoa framework uses to report problems across macOS and iOS — it covers everything from file access issues to UI failures to data problems. Error code 4 within that domain narrows things down to a “resource not found” condition: something the system or an app expected to exist at a specific reference point simply isn’t there anymore.
The message itself — “could not find the specified shortcut” — is unusually literal for an Apple error. It means a workflow, automation, or app tried to run a named shortcut, and that shortcut no longer exists where it’s expected to.
This shows up constantly in three specific contexts: running a custom shortcut directly from the Shortcuts app when it references another shortcut that’s been deleted, triggering a personal automation that points to a shortcut no longer in your library, or a third-party app calling into Apple’s Shortcuts framework (via SiriKit or App Intents) for a shortcut that’s since vanished.
The iCloud Sync Trap Most Guides Miss
Here’s a detail that explains a genuinely confusing version of this error: if your shortcuts sync through iCloud — which they do by default for most users — deleting a shortcut on one device removes it everywhere.
So if you deleted (or accidentally overwrote) a shortcut on your Mac last week, and you’re now seeing this error trying to run something on your iPhone that references that same shortcut, the iPhone genuinely cannot find it, because it’s gone from every synced device simultaneously, not just the one you deleted it on.
This is worth checking before anything else, because the fix is completely different depending on whether you’re dealing with a genuinely deleted shortcut versus a sync glitch. If the shortcut shows up as missing across all your devices uniformly, it’s a real deletion — recreate it or restore from an iCloud backup, and it should propagate back out everywhere.
If it only seems to be missing on one device while others can still see it, you’re more likely looking at a sync delay or glitch, and a straightforward restart or forcing a fresh sync often resolves it without rebuilding anything.
Fixing It Inside the Shortcuts App Itself
Start here before touching system files or reinstalling anything, since this resolves the large majority of cases:
Open the Shortcuts app and look specifically at any automation or shortcut that calls another shortcut by name — these chained references are the most common failure point. If a shortcut you’re trying to run includes a step like “Run Shortcut” pointing at something that’s been renamed or deleted, that single broken link is enough to throw this exact error even though the rest of the shortcut is perfectly intact.
Rebuilding it is usually faster than debugging it. If you can identify which referenced shortcut is missing, recreate it under the same name, or open the broken shortcut and re-point that specific step at the correct (or rebuilt) target. Saving it under a fresh name afterward avoids any lingering reference conflicts with the old, broken version.
If you’re working with Automator workflows or AppleScript instead of the Shortcuts app directly, the same underlying problem applies — an action like “Run Shortcut” or a script line calling tell application "Shortcuts Events" to run shortcut named "X" will throw this exact error if “X” no longer exists under that name. Reselecting the correct item in Automator, or correcting the name in the script, resolves it the same way.
When It’s Genuinely a File-Path Problem Instead
The error code can technically apply more broadly than just the Shortcuts app — any Cocoa-based reference to a missing file, alias, or path can trigger the same NSCocoaErrorDomain code 4. This is less common in practice, but worth ruling out if you’ve already confirmed the Shortcuts app itself looks fine.
A few things point to this broader cause rather than the Shortcuts-specific one: the error appearing in an app that has nothing to do with automation, happening consistently after a recent app update (which can shift internal file structures and orphan old references), or showing up alongside other unrelated app misbehavior rather than specifically when running an automation.
In these cases, checking Console.app for the specific file path the system was attempting to reach is the fastest way to confirm what’s actually missing — it’ll show you the literal path in the error’s underlying log entry, which tells you immediately whether you’re chasing a shortcut or a stray file reference.
The General Troubleshooting Path, in the Right Order
Restart the device first — this clears transient cache state and resolves a surprising share of one-off occurrences without any deeper investigation needed.
If that doesn’t help, check whether a pending macOS or iOS update is available; Apple has shipped fixes for Shortcuts-related bugs in past system updates, and running an outdated version is a documented cause of this exact error reappearing for no obvious reason.
For persistent cases tied to a specific app rather than the Shortcuts app itself, move a suspect .plist file out of ~/Library/Preferences/ (to your Desktop, not deleted, in case you need it back) and relaunch the app — if the error disappears, the preference file was corrupted and the app will rebuild a clean one automatically.
Clearing that app’s folder in ~/Library/Caches/ alongside this step covers the same category of cause.
If none of that resolves it and the error shows up across multiple unrelated apps, that’s a sign worth taking seriously. Running Disk Utility’s First Aid pass against your main volume is the appropriate next step at that point, since it directly checks for and repairs the kind of underlying corruption that produces exactly this scattered pattern.
Keeping This From Coming Back
A few habits meaningfully cut down how often this resurfaces. Treat shortcuts that reference other shortcuts with a bit of caution — chained dependencies are inherently more fragile than a single self-contained shortcut, since deleting or renaming any link in the chain breaks everything downstream of it.
If you maintain automations you rely on regularly, periodically open them and confirm every referenced step still points to something that exists, especially after you’ve done any cleanup of your shortcut library.
Keeping the Shortcuts app and your OS reasonably current matters more here than with most apps, since Apple has specifically patched sync and reference bugs in past updates.
And if you’re someone who builds a lot of chained automations, documenting which shortcuts depend on which others — even just a simple note — saves real troubleshooting time later, since the error itself won’t tell you which specific link in a multi-step chain actually broke.
Frequently Asked Questions
Does this error mean I lost data?
No — it indicates a broken reference to a shortcut or file, not data loss. Your actual files and content remain intact; only the link pointing to one specific item is missing.
Why did my shortcut disappear from all my devices at once?
If iCloud sync is enabled for Shortcuts, deleting or overwriting a shortcut on one device removes it from every synced device simultaneously — this is expected sync behavior, not a separate bug.
Can a macOS or iOS update actually cause this error?
Yes — updates occasionally change internal file structures or reset shortcut references, which can surface this error until you update again or rebuild the affected shortcut.
Is this always related to the Shortcuts app specifically?
Most commonly yes, but the same error code can technically apply to any missing file or path reference in a Cocoa-based app — Console.app’s logged file path will tell you which case you’re actually dealing with.
What’s the fastest fix if I just need it working again right now?
Open Shortcuts, find the broken or referenced shortcut, and recreate it under the same name — this resolves the large majority of cases faster than any system-level troubleshooting.
