How to Fix IFTTT Applets That Stopped Running

If your lights used to turn on at sunset, your plugs used to follow a voice command, or your phone used to log your arrival home — and then one day nothing happened — you are not alone. Many IFTTT users found their favourite applets quietly stopped running after the free plan limits changed, and the service tightened how many applets free accounts could keep active at once.

The good news is that most broken applets are not truly broken. They are paused, archived, disconnected, or sitting above a new limit. In this guide you will learn how to check exactly why an applet stopped, how to fix IFTTT applets for smart home that stopped running after the free plan limits changed, and when it makes more sense to rebuild the same automation inside your smart home hub instead.

Quick Answer

To fix IFTTT applets that stopped running, sign in to IFTTT, check which applets are still connected and whether you are over the free plan applet limit, then disconnect and reconnect the smart home services involved. Turn off or archive applets you no longer need so your most important bedtime, lighting, and security applets sit within the limit. Test each repaired applet manually, check its activity log for errors, and move any critical automation to Home Assistant, SmartThings, or Apple Home if you need it to run reliably without a subscription.

What Actually Changed With the Free Plan

IFTTT built its name on simple if-this-then-that rules. For years, free users could create many custom applets and keep them running at once. When the paid Pro plans arrived, the free tier was narrowed. The exact numbers have been adjusted over time, so always check your current account page rather than relying on an old blog post.

In practical terms, three things catch people out:

• Only a limited number of applets can be enabled at once on a free account. Extra applets may be archived or turned off automatically.
• Some advanced features — multi-action applets, filter code, and faster polling — are reserved for paid tiers, so an edited applet may no longer save in its old form.
• Connected services sometimes need re-authorising after plan or permission changes, especially for Google, Amazon, and smart home brands that updated their sign-in methods.

None of that deletes your devices. Your bulbs, plugs, and locks still work in their own apps. IFTTT is only the bridge between services, and it is that bridge you are repairing. You can confirm the current limits and features in the official IFTTT help centre, which lists plan details and troubleshooting steps for disconnected services.

Step 1: Audit Your Applets Before You Change Anything

Resist the urge to delete everything and start again. A five-minute audit saves a lot of rebuilding.

1. Sign in to IFTTT on the web, not just the mobile app, so you can see the full list clearly.
2. Open My Applets and note which ones say Connected, which are off, and which are archived.
3. Write down your five most important smart home applets — for example, sunset lights, door sensor alerts, and thermostat schedules.
4. Open one broken applet and tap Activity or View Logs, if available. Look for plain-English errors such as service disconnected, trigger failed, or applet skipped.
5. Check your email for messages from IFTTT about a service needing attention. Those alerts often name the exact brand connection that expired.

By the end of this audit you should know whether you have a limit problem, a connection problem, or a trigger problem. Each one has a different fix, and guessing wastes time. If your wider setup has grown messy over the years, our guide to organising your smart home apps and automations can help you decide which rules should live in IFTTT and which should move to your hub.

Step 2: Get Back Under the Free Limit

If you are over the limit, no amount of reconnecting will make every applet run at once. You need to choose winners.

1. Turn off applets you created to test an idea and never used again.
2. Archive duplicate applets — many users accidentally have two sunset lighting rules from different years.
3. Combine simple actions where your plan allows it, or move combined actions into a single scene in your smart home app and let IFTTT trigger only that scene.
4. Keep security, lighting, and heating applets at the top of your list. Move novelty applets, like changing light colours for sports scores, to the bottom.
5. After trimming, make sure your must-have applets are switched on and show as Connected.

Step 3: Reconnect the Smart Home Services

Expired connections are the second most common cause. A brand updates its login, you change a password, or a token expires, and IFTTT silently stops passing commands.

1. In IFTTT, go to Settings or Services and open the smart home service named in the error, such as Philips Hue, SmartThings, Wyze, or your thermostat brand.
2. Tap Reconnect or Edit Connection and sign in again with the correct account. Make sure it is the same account that owns the devices in the brand app.
3. Grant all the permissions IFTTT asks for. Missing a permission for a home or location is a frequent hidden cause.
4. Repeat for the other side of the applet. An applet has a trigger service and an action service — either one can be the broken link.
5. Go back to the applet, turn it off and on once, and run a manual test if the service offers one.

Step 4: Check the Trigger Itself

Sometimes the connection is fine and the applet is under the limit, but the trigger no longer fires the way it used to.

• Location triggers: Phone battery savers and revoked location permissions stop arrival and departure applets. Allow IFTTT to use location in the background.
• Time and weather triggers: Check the time zone and city are still correct, especially after travel or a phone change.
• Voice triggers: If you use Alexa or Google Assistant, confirm the phrase still matches and the assistant account is the same one linked to IFTTT.
• Sensor triggers: Open the brand app and confirm the sensor itself reports motion, contact, or temperature correctly before blaming IFTTT.

Change one thing at a time and test after each change. If you fix three settings at once, you will never know which one mattered when the next applet breaks.

Step 5: Test Properly and Watch the Log

1. Trigger the applet on purpose — walk past the sensor, say the phrase, or wait for a short test schedule you set two minutes ahead.
2. Watch whether the action happens within the expected delay. Free plans may poll some services less often, so a delay is not always a failure.
3. Open the applet activity feed again and confirm a successful run with no warning.
4. Leave the applet running for 24 hours and check once more the next day, because some triggers only fire once daily.

Common Mistakes to Avoid

• Deleting and recreating everything. You lose your history and often recreate the same limit or permission problem.
• Using the wrong account. Many homes have two Hue, Google, or Amazon accounts. IFTTT must be linked to the one that actually owns the devices.
• Ignoring archived applets. An archived applet looks present but will not run. Check its status, not just its title.
• Expecting instant polling on a free plan. Some triggers are checked on an interval. For security-critical alerts, use your hub or brand app notifications instead.
• Leaving old applets on. Every forgotten test applet that stays enabled eats into your limit and clutters your troubleshooting.

When to Move the Automation Off IFTTT

IFTTT is still excellent for linking services that do not normally talk to each other. It is less ideal as the only home for critical routines. Consider moving an automation to SmartThings, Home Assistant, Apple Home, or Google Home if it must run during an internet outage, if it involves door locks or alarms, or if you need it to fire within a second or two. Keep IFTTT for helpful extras — notifications, logging, weather-based tweaks, and cross-brand conveniences — and let your hub handle the essentials. That split gives you reliability where it counts and flexibility where it is fun.

Conclusion

Most IFTTT applets that stopped after the free plan changes can be revived with a calm audit: check the limit, reconnect the services, verify the trigger, and test with the activity log open. Trim the list to the automations you truly value, and move critical smart home rules to your main hub for long-term peace of mind. With that done, your sunset lights, alerts, and schedules should run again — and you will know exactly what to check first if they ever pause in future.

Frequently Asked Questions

Did IFTTT delete my applets when the free plan changed?

Usually not. In most cases applets were turned off or archived rather than deleted. Sign in on the web, open My Applets, and check the archived and disconnected sections before you rebuild anything from scratch.

How do I know if I am over the free applet limit?

Open your account and plan page in IFTTT and compare the number of enabled applets with the limit shown for your current plan. If extra applets will not stay on, the limit is the most likely reason.

Why does my applet say connected but still not run?

The trigger service, the action service, or a phone permission may still be broken even when the applet looks connected. Check the activity log, test the trigger in its own app, and reconnect both services.

Will paying for IFTTT Pro fix all my broken applets?

Not automatically. Pro raises limits and unlocks features, but an expired brand login or a wrong location permission will still block an applet. Fix the connections first, then decide if you need the higher limit.

Can I run the same automation in IFTTT and my hub at the same time?

You can, but it often causes double actions, like lights toggling twice. Pick one home for each automation, test it, and turn the duplicate off to keep behaviour predictable.