Start with the App Limit itself: the apps it covers, its shared daily allowance, its days, and the overrides Screen Time intentionally offers. This guide is for App Limits—not every Screen Time problem.
First, work out whether the App Limit triggered. If you see Ignore Limit, the limit reached its allowance; that is an expected override, not proof that the rule failed. If the allowance seems to run out too soon, view the detailed iPhone Screen Time report before changing the rule’s selection or days. For the bigger question behind all of this, see what the evidence actually says about whether app blockers work.
For Downtime, shared-device, configuration, or system-wide Screen Time problems, use the broad Screen Time troubleshooting guide.
| What you're seeing | What's actually happening | Where to fix it |
|---|---|---|
| Limit hits, shows "Ignore Limit" | The limit is working as designed, with an override | Turn off Ignore Limit |
| Limit silently stops enforcing | The selected app, allowance, days, or Always Allowed setting needs checking | Inspect and rebuild this App Limit |
| Works on one device, not another | Screen Time settings may be shared across devices | Check shared-device settings |
| Limit affects the wrong apps | The category or app selection does not match what you expected | Test one individual app first |
| Grouped apps share time faster than expected | Multiple apps under one limit share a single time pool | Split apps into separate individual limits |
| A fresh individual-app limit still does not trigger | The issue may be broader than this one App Limit | Run the broader checks above |
1. Selected app or category. Confirm the rule covers the intended app or category. Apple lets you select whole categories or open a category and choose individual apps.
2. Shared allowance. Apps selected together share one time pool, not separate allowances. Spend the whole limit in one selected app and the others can be blocked too.
3. Customize Days. Open the affected limit and check the allowance assigned to each day. A custom day can have a different limit from the default.
4. Always Allowed. Remove the affected app from Always Allowed before testing the App Limit again.
5. App & Website Activity. Confirm it is turned on. Turning it off also turns off reporting, Downtime, App Limits, and Always Allowed.
6. Share Across Devices. Check whether Screen Time is sharing limits and usage across devices signed in to the same Apple Account.
App Limits and Downtime solve different problems. App Limits set a daily allowance. Downtime applies at scheduled times; with Block at Downtime enabled, restricted apps cannot be opened during that window. For basic configuration, use the separate guide to set App Limits on iPhone.
Open Settings > Screen Time > App Limits and tap the rule that is failing. Write down its apps, categories, time allowance, and Customize Days settings, then delete only that limit. Restart the iPhone and create a fresh rule for one individual app first.
Use a one-minute allowance for the test. Remove the app from Always Allowed, then use the app until the minute expires. An individual-app test avoids category mismatches and grouped time pools, making the result easier to interpret.
If the new rule works, add other apps one at a time or keep separate allowances. If it fails, check App & Website Activity, the software version, and Share Across Devices. If the reported usage itself looks wrong, see how to troubleshoot inaccurate iPhone Screen Time.
Rebuilding all of Screen Time is a last step because turning off App & Website Activity also turns off reporting, Downtime, App Limits, and Always Allowed. Record every restriction first, especially on a child’s device.
1. Record your configuration. Note your App Limits, Downtime schedule, and Always Allowed apps before changing anything.
2. Turn off App & Website Activity. In Settings > Screen Time, turn off App & Website Activity. Apple notes that this also turns off reporting, Downtime, App Limits, and Always Allowed.
3. Turn it back on and recreate the affected rules. Start with one App Limit for one app, then add the other rules after that test behaves as expected.
4. Check the right feature. If the goal is scheduled restricted hours rather than a daily allowance, set up Downtime and turn on Block at Downtime.
App Limits are useful for a daily time budget, but they are easy to misread when the selection, shared allowance, and expected override are not clear.
Fella uses a single list of blocked apps. Apps you choose stay blocked by default, with one 5-minute emergency unlock per blocking session. If the warning appears correctly but you still tap through it, see how to handle a Screen Time limit you keep overriding.
Yes. When you select several apps for one limit, their usage counts together against a single shared time pool, rather than each app getting its own separate allowance.
Yes. App Limits set a daily time allowance for selected apps or categories. For scheduled restricted hours, use Downtime instead.
App Limits set a daily allowance for chosen apps or categories. Downtime applies during scheduled hours; with Block at Downtime on, restricted apps cannot be opened during that window.
Check App & Website Activity, the selected apps, Customize Days, Always Allowed, iOS updates, and Share Across Devices. If the issue remains, record the current configuration and rebuild the affected Screen Time rules.
Only if the limit is triggering correctly and showing Ignore Limit. If no warning appears, first check the App Limit’s selected apps, allowance, Customize Days settings, and Always Allowed.
Apps selected together in one limit share the same daily allowance. Create a separate limit for each app if you want each one to receive its own time budget.
