Screen Time Limits
Why Screen Time limits
stop working.
Sometimes it's the Ignore Limit button. Often it's a real bug or a setting quietly overriding another one. Here's how to tell which, and what to actually fix.
"Not working" usually means one of two different things. Either the limit is technically active but has an easy override, which is a design choice covered in how to deal with the Ignore Limit button, or the limit silently stops enforcing on its own, which is a genuine bug or misconfiguration.
The second bucket is more common than people expect. Screen Time settings sync across iCloud, apply per-app and per-category with their own precedence rules, and depend on an Always Allowed list that quietly overrides everything else. Any one of those layers can fail without changing what the settings screen shows you.
This page covers the second bucket: the real, documented reasons a Screen Time limit stops working even when nobody touched it.
The most common reasons Screen Time limits fail
"Block at End of Limit" isn't turned on. Without this specific toggle enabled, hitting a limit shows a warning screen with an Ignore Limit button instead of actually blocking the app. Many people set a limit and assume it blocks by default; it doesn't unless this is on.
The app is on the Always Allowed list. Always Allowed apps skip both App Limits and Downtime entirely. If a limit doesn't seem to apply to a specific app, check whether it's sitting on that list, whether you added it there or not.
The app is miscategorized. Apple's category assignments aren't always accurate; some games are labeled as education apps and vice versa. A category-based limit does nothing for an app Apple filed somewhere else.
An "All Apps & Categories" limit is overriding a narrower one. If you set both a broad limit for all apps and a specific limit for one category, the broader limit can take precedence in ways that make the narrower limit look like it's being ignored.
iCloud sync dropped. Limits sync between your devices and iCloud through Share Across Devices. A restart, a signed-out Apple ID, a connectivity drop, or simply low storage can interrupt that sync, and limits can silently disappear until it resyncs.
The device date and time are wrong. Screen Time depends on the device clock to track and trigger limits. With "Set Automatically" off and an incorrect date or time, limits and downtime can fail to fire on schedule.
Documented iOS bugs. Apple's own community forums and iOS release notes have repeatedly logged cases where App Limits stop enforcing after an update, sometimes tied to specific settings like short time extensions, with no configuration error on the user's part.
| Symptom | Likely cause | Fix |
|---|---|---|
| Limit hits, app still opens | "Block at End of Limit" is off | Turn it on for that specific limit. |
| One app ignores its limit | App is on the Always Allowed list | Remove it from Always Allowed. |
| Category limit does nothing for an app | App is miscategorized by Apple | Set an individual app limit instead of a category limit. |
| Limits differ between devices | Devices aren't syncing | Check Share Across Devices, the same Apple ID, and connectivity on both devices. |
| Limit worked yesterday, gone today | iCloud sync interruption | Toggle Share Across Devices off and back on to force a resync. |
| Everything looks right but nothing triggers | Wrong device date or time | Turn on Set Automatically under Date & Time. |
When it isn't a bug
If the limit fires correctly and the app still opens, that's not a malfunction. That's the Ignore Limit button working exactly as Apple designed it, and it's a separate problem from the ones above. See how to remove the Ignore Limit button and app limits not working on iPhone for that specific issue.
Fewer layers, fewer ways to break
Most of the failure modes above come from Screen Time's own configuration depth. Categories, Always Allowed exceptions, All Apps & Categories overlaps, and a separate Block at End of Limit toggle are all places where one setting can quietly override another.
Fella uses one block list instead of that stack. You pick the apps you want blocked, once, and there's no category system, no Always Allowed exceptions, and no broad-versus-narrow limit conflict for those specific failures to hide in.
That doesn't mean Fella is immune to every issue on this page. Fella still runs on Apple's underlying Screen Time frameworks, so device-level sync problems are Apple's infrastructure, not something any third-party app can fully control. What Fella removes is the layered configuration that causes most of the other failures above.
Screen Time troubleshooting FAQ
This is usually an iCloud sync interruption. Screen Time settings sync between your devices and iCloud, and if that sync is interrupted by a restart, a signed-out account, or a connectivity drop, limits can silently disappear without any visible change in the settings screen.
The most common cause is that "Block at End of Limit" is not turned on for that limit. Without it, reaching the limit shows a warning screen with an Ignore Limit option instead of actually blocking the app.
Yes. Any app on the Always Allowed list bypasses both App Limits and Downtime entirely, regardless of what limit you've set for it or its category. It has to be removed from Always Allowed before a limit will apply to it.
Devices need to be signed into the same Apple ID with "Share Across Devices" enabled, connected to the internet, and set to the correct date and time automatically. If any of those is off, limits can apply on one device and not another.
Both happen, and they look similar from the outside. A bug usually means the limit silently stops enforcing with no visible change to settings. Bypassing usually means a visible action was taken, like tapping Ignore Limit, disabling Screen Time access, or borrowing another device.
Yes. Screen Time relies on the device clock to track and enforce limits, so if Set Automatically is off and the date or time is wrong, limits and downtime can fail to trigger correctly.
Fella uses one block list instead of App Limits, categories, Always Allowed exceptions, and All Apps & Categories overlaps, so there's no layered configuration for those specific conflicts to happen in. It still depends on Apple's underlying Screen Time frameworks, so device-level sync issues can still occur.
See also how to remove the Ignore Limit button, app limits not working on iPhone, the strict app blocker for iPhone guide, or the Screen Time alternative page.