Which iPhone automations still fire inside a Work Focus that blocks every other app?

The ones that do not need a blocked app on screen. Inside a Work Focus that allows only Phone and one work app, time-of-day automations, charger automations, and Shortcuts set to run immediately still fire if their steps stay on the phone: set a Focus, run a Home scene, start a timer. They do not fire in any way you can see if Ask Before Running is on, because the banner is hidden with everything else. They do not successfully Open App for Slack, Mail, or Shortcuts itself when those apps are not on the allow list.

Work Focus blocks apps and notifications. It does not switch off the automation engine. People think the shortcut died because the notification died. The light still changed. The banner did not.

What still runs while almost every app is blocked?

A personal automation with Ask Before Running turned off. The trigger can be a time, the charger, connecting to the office Wi-Fi, or the Work Focus itself turning on. The steps that finish are the ones that do not launch a forbidden app. Control Home. Set a Focus or leave Work on. Play audio if the system is allowed to, even when the Music app icon is hidden. Append a note only if that action does not have to open a blocked notes app in front of you. Set a timer. Those complete with the Home Screen showing two icons and nothing else.

Alarms in the Clock app still fire. A Focus that silences the world does not eat an alarm you set as an alarm. A reminder that is only a notification may be silenced. If the thing must make a sound at 5, use an alarm, not a reminder and not a Shortcut that posts a banner. The banner is exactly what Work Focus is for hiding.

Phone calls from the people you allowed in the Focus still ring. That is the Focus’s own allow list, not a Shortcut. If you allowed nobody, the phone is quiet and the automation engine is still awake. Do not confuse a silent phone with a phone that stopped evaluating triggers.

What looks dead and is only invisible?

Notify When Run. The shortcut ran. Work Focus hid the Shortcuts notification because Shortcuts is not an allowed app. You will swear the 9 a.m. automation stopped the day you made Work strict. Check the thing the shortcut changes. The lamp. The other Focus. The file. If that changed, it ran. Turn on a notification for Shortcuts inside this Focus only if you truly need the banner, and accept that you punched a hole in “blocks every other app.”

Ask Before Running is worse. The prompt is a notification. Work Focus swallows it. The automation waits for a tap you will never see, then does nothing. For any automation that must run during Work, turn the ask off, and keep the steps safe enough that an unseen run is acceptable. If the steps are not safe, this Focus is the wrong place for that automation. A tap you have to see does not belong inside a Focus built to hide taps.

Which steps fail because the app is blocked?

Open App, for any app not on the Work allow list. The automation can start and then stop at that step. Mail, Slack, Safari, the Shortcuts app, Maps. If your “start work” shortcut ends by opening the work chat, either allow that app in the Focus or delete the Open App step. The Focus already put you in work. Opening the app is a second job the block list exists to refuse.

Show Alert, Choose from Menu, and Ask for Input need the screen and an answer. During a strict Work Focus you may not see them, or you see them and they are the interruption you built the Focus to prevent. Take them out of automations that run while Work is on. A menu at 9 a.m. is a meeting you scheduled with yourself and then hid.

Send Message often still wants confirmation, and the confirmation is a UI event on a phone that is trying not to show you anything. Do not put a text in a Work automation and expect it to leave unseen. It will wait. That wait is the correct behavior. Move the text to a moment you are looking at the phone.

Do location and the office Wi-Fi still count?

Yes. Arriving at work can still turn the Focus on, and automations tied to that Wi-Fi can still run, even while the Focus then blocks the apps. The order matters. If the automation opens Slack, and the Focus turns on first and blocks Slack, the open fails. If the automation only sets a scene and the Focus handles silence, both succeed. Put the silence in the Focus. Put one local action on the trigger. Do not also open the app the Focus just forbade.

Leaving work is the automation people forget. The Focus should end on its schedule or when you leave, without a Shortcut that has to show a banner to turn itself off. If Work only ends because you tap a shortcut, and that shortcut’s notification is hidden, you will eat dinner inside Work. Give the Focus its own end. A shortcut that also runs when Work ends can turn lights on, quietly, with Ask Before Running off.

What you should allow, if “every other app” was slightly too proud

Allow Shortcuts notifications only for a week while you test, then hide them again once you trust the side effect. Allow the one work app you actually have to open. Allow Phone and the people who can interrupt. Do not allow Mail “just in case” if the point of the Focus was to stop mail. A Focus that allows every app you might automate is the Focus you had before you got strict, and the question goes away because nothing is blocked.

Low Power Mode and a lock screen stack on top of this. A Work automation that also fetches a URL can fail for those reasons while the Focus is innocent. Test the shortcut in the middle of a Work day, unlocked, with the Focus on, and watch the steps. Then test it locked. The Focus is only one of the gates.

How a watch and a Mac confuse the test

An Apple Watch can still tap a complication and run a phone Shortcut while the iPhone is in Work Focus. That run hits the same app blocks. The watch feeling responsive does not mean Slack opened on the phone. It means the watch sent a trigger. Check the phone’s side effect, not the haptic.

A Mac that shares Focus will go quiet too, and a Mac shortcut is a different machine. Do not debug the iPhone automation by seeing whether the laptop hid notifications. The laptop hid them because Focus syncs. The iPhone automation either changed the house or it did not. Those are separate facts. I have “fixed” an iPhone shortcut for an hour because the Mac was silent, and the lamp had been right the whole time.

Driving Focus and Sleep can also be on, or fighting Work, if you stacked schedules. Two Focuses do not merge into a kinder allow list. One wins. If Work is supposed to be the strict one and Sleep turned on at the wrong hour, the automations you attributed to Work were running under Sleep, with a different set of silenced apps. Look at the Focus icon before you edit the shortcut. The icon is the policy that was actually applied.

1. Automations with Run Immediately and no Open App still fire during a strict Work Focus.
2. Banners do not. Ask Before Running will stall unseen. Turn it off or do not expect the run.
3. Alarms and allowed calls still happen. Reminders that are only banners may not.
4. Opening a blocked app fails. Delete that step or allow the app.
5. Give Work its own end. Do not depend on a hidden notification to turn it off.

Shortcuts widgets on a Lock Screen you allowed for Work are still taps, not background runs. If the widget opens a blocked app, the tap fails the same way Open App fails. If the widget only toggles a Home scene, it works, and it works because you touched it. Do not count that tap as proof that the 9 a.m. automation is alive. One had a thumb. The other had a schedule and a hidden banner. Test the schedule once, in the middle of Work, with the phone locked, and judge it by the scene or the lamp rather than by whether the widget still exists.

A Work Focus that blocks every other app does not block the automations that never needed those apps. It blocks the evidence, the prompts, and any step that tries to open what you forbade. If the shortcut’s only proof was a banner, you did not test it. Look at the lamp.