# “Automation Failed” in Shortcuts? What Each Error Means

> Automation failed, Shortcut Timed Out, There was a problem running the action. What each Shortcuts error on iPhone means, and how to fix the step.

Last updated: 2026-11-04
Canonical HTML page: https://www.fwrdsms.com/blog/shortcuts-automation-failed
Published: 2026-11-04

“Automation failed” means the automation started but one of its steps stopped with an error, so the steps after it didn’t run. Open Shortcuts, run the automation’s shortcut by hand, and the step that stops is the one to fix. The message that comes with it, such as Shortcut Timed Out or There was a problem running the action, says what kind of problem it is.

**What you need:** the iPhone with the automation, the Shortcuts app, and the name of the automation that failed. The fixes below are for a Message automation, the kind that runs when a text arrives, and most apply to any trigger.

## What does “Automation failed” mean?

The trigger worked: a text arrived, it matched the rule, and the automation started. Then a step couldn’t finish. Shortcuts stops at that step, so nothing after it happens, and it tells you with a notification.

That’s different from an automation that never runs at all. If nothing happens and no notification appears, the automation is switched off, set to ask first, or the text didn’t match. [Shortcuts automation not running?](https://www.fwrdsms.com/blog/shortcuts-automation-not-running) covers that case.

## What each Shortcuts error means

These are the messages Shortcuts shows, word for word, and what usually causes each one:

| Message | What it usually means | Fix |
|---|---|---|
| Automation failed | A step stopped with an error | Run the shortcut by hand to find the step |
| There was a problem running the action. | One action couldn’t finish | Open that action and check its settings |
| There was a problem opening the app, with a request to open the iPhone first | A step tried to open an app on a locked iPhone | Remove the step, or set it not to open the app |
| There was a problem communicating with the app. | An app’s action couldn’t reach its app | Open the app once, update it, then try again |
| Shortcut Timed Out / The shortcut took too long to run. | A step waited too long, often on the network | Check the connection, or shorten the shortcut |

## How to find the step that failed

1. **Open the automation.** On iOS 27, open Shortcuts, tap Library, then Automation, and tap the one that failed. If it opens on a description, tap Edit. On iOS 26, tap Automation at the bottom, then the automation.

2. **Run it by hand.** Tap the play button. Shortcuts runs each step in order and stops at the one with the problem, showing the error. Run by hand, there’s no text to pass along, so a step that needs the message can stop for that reason alone.

3. **Fix that step.** Fill in any empty field, choose a fixed value where it asks a question, and on Send Message and Send Email, turn Show Compose Sheet off.

4. **Run it again** until it reaches the end without stopping.

5. **Lock the iPhone and send a matching text** from another phone. If it fails only when locked, a step needs the screen. [Automation not running when locked](https://www.fwrdsms.com/blog/shortcuts-automation-not-running-when-locked) covers those switches.

## Why does it fail only sometimes?

When the same automation works most of the time, the step usually depends on something outside the shortcut:

- **The network.** A step that sends something over the internet waits for an answer. With weak Wi-Fi or signal it can take too long, and Shortcuts gives up with Shortcut Timed Out.
- **A restart.** After any restart, iPhone keeps saved passwords locked until you unlock it once, so apps that need them can’t finish their step until then.
- **The app on the other end.** A service that’s down, or that turns the message away, makes the step fail even though nothing changed on the iPhone.

## If the failing step is Fwrd’s

[Fwrd](https://apps.apple.com/app/apple-store/id6759069713?pt=128544281&ct=blog-auto-failed&mt=8)’s action doesn’t open the app or ask a question, so it runs on a locked iPhone. When a text doesn’t arrive where Fwrd sends it, open Activity in Fwrd:

- **The text isn’t listed:** the automation didn’t reach Fwrd’s step. Fix the step before it, or the automation itself.
- **It’s listed as Failed:** tap it to see why, such as a destination that turned it down or a webhook address that’s no longer valid. Fix that destination in Fwrd, and tap Send Test Message.

Email, another phone and WhatsApp are sent by Apple’s or WhatsApp’s own action after Fwrd’s, so a failure there is that action’s: check its compose sheet and recipient.

## What these errors can’t tell you

- **They don’t name the cause.** Running the shortcut by hand is how you find the step.
- **They don’t retry.** A text whose automation failed isn’t sent again by itself.
- **They can’t fix a turned-off automation.** No run, no error: check its switch instead.
- **They can’t stop the iPhone from restarting.** After three days without an unlock, iPhone restarts itself, and apps that need saved passwords wait until it’s unlocked once.

## Questions about Shortcuts errors

### Why does my iPhone say “Automation failed”?

A step in the automation stopped with an error. Open the automation in Shortcuts and run it by hand: it stops at the step with the problem, and that’s the one to fix.

### What does “Shortcut Timed Out” mean?

A step waited too long to finish, usually for an answer over the internet. Check the iPhone’s Wi-Fi or signal, and remove any step that waits, such as Wait or a slow web request.

### How do I stop the “Automation failed” notification?

Fix the step that fails, and the notification stops with it. Turning off the automation also stops it, but then the automation doesn’t run either.

## Keep reading

- [Shortcuts automation not running? Fixes for iOS 26 and 27](https://www.fwrdsms.com/blog/shortcuts-automation-not-running)
- [Shortcuts automation not running when locked](https://www.fwrdsms.com/blog/shortcuts-automation-not-running-when-locked)