You set up an Alexa routine. You trigger it manually from the app and it fires perfectly. You wait for the trigger condition (a specific time, a motion event, a voice phrase) and nothing happens. The routine that worked yesterday silently does not work today. The Alexa app gives no indication that the routine even attempted to run.
Check the trigger source first
Routines fail to trigger for one of four reasons:
- The trigger device went offline
- The trigger condition is misconfigured
- The Alexa device that owns the routine is offline or muted
- The routine was disabled inadvertently
Start with the trigger source. If your routine triggers on motion from a Wyze Cam, verify the Wyze Cam is online in the Wyze app, not just in Alexa. Alexa sometimes shows devices as online based on stale data when the device is actually offline.
The voice trigger pitfall
Voice-triggered routines depend on the exact phrase. “Alexa, goodnight” and “Alexa, good night” are different triggers. The Alexa app lists your routine triggers in the routine’s settings. Compare what is listed to what you actually say. A subtle word change is the most common cause of voice routines that suddenly stop working.
If you set up the routine months ago and forgot the exact phrase, the app shows it. Update if needed.
Time-based triggers and time zones
If your routine triggers at 7 AM, it triggers at 7 AM in the time zone assigned to the Alexa device. If the device’s time zone is wrong, the routine fires at the wrong time. Check the Alexa device’s settings under “Device location”. If your home is in Eastern time but the device thinks it is in Pacific, your 7 AM trigger fires at 10 AM by your wall clock.
Daylight saving transitions sometimes shift routine times by an hour for one or two days while Alexa syncs. This usually self-corrects.
Sunrise and sunset triggers
Routines that fire “at sunset” rely on Alexa knowing your home location. If you have moved or your home address is incorrect in Alexa’s settings, the sunset trigger fires at the wrong time. Update the home address under Settings, Your Locations.
Device trigger conditions
If your routine triggers on a smart device event (door open, motion detected), the device must report state changes back to Alexa. Some devices report quickly, others have a reporting interval that can be minutes long.
Test by manually triggering the device and watching the Alexa app for state change confirmation. The app should reflect the state change within 30 seconds for most devices. If it takes longer or never reflects, the device is not reporting back to Alexa, which means routine triggers will not work either.
The Alexa cloud sync issue
Routines sync from Alexa’s cloud to your devices periodically. If you edit a routine on your phone, it can take several minutes to propagate to the Echo speakers in your home. If a routine fires from an Echo, the Echo must have the current version of the routine.
To force a sync, open the Alexa app, navigate to the routine, edit it (even just open and close it), and tap Save. This pushes the latest version to all your Echos within a minute.
Routine ownership matters
Each routine is owned by a specific Alexa device. If the owner device is offline or has been removed from your account, the routine never fires. Routines that have no owner (set to “any device”) are more resilient.
In the routine settings, check “From” or “Trigger device”. If it specifies a particular Echo and that Echo is offline, change it to “Any device” or to a different healthy Echo.
Routine actions also fail silently
Sometimes the routine triggers correctly but the action fails silently. If your routine turns on a smart light and the light is offline, you do not see an error. The trigger fired; the action just had nowhere to land.
To diagnose, look at the action devices in your Alexa app. Are they showing as online? Do they respond to manual commands? If not, the action’s targets are the problem, not the routine.
The skill dependency
If your routine depends on a third-party skill (Ring, Nest, IFTTT), and the skill linkage has broken, the routine fails. Skill linkages break when the third-party service rotates its OAuth tokens, when you change your password, or when the manufacturer updates the skill.
Go to More, Skills & Games, Your Skills. Look for the relevant skill. If it shows a warning or asks you to re-authorize, that is your problem. Re-authorize the skill and the routine actions should resume working.
Disabled or paused routines
Routines can be disabled accidentally. Open the routine, check the toggle at the top. If it shows disabled, enable it. This is more common than people admit; a swipe in the routine list can disable without confirmation.
Multiple Alexa accounts
If your household has multiple Alexa accounts (for example, you and a spouse both have separate accounts but use the same Echos), routines are scoped to the account they were created in. A routine you created may not see triggers fired by your spouse’s account, and vice versa.
Switching to Household profiles (where all accounts in the home share routines and devices) usually fixes this. The settings are under Communications, Profile.
What the Alexa app does not tell you
The Alexa app does not show a history of routine triggers. There is no log of “routine attempted to run at 7:01 AM, failed because target device was offline”. This makes diagnosing intermittent issues hard.
The workaround is to create a debug routine: when the same trigger fires, also send a notification to your phone. The notification will arrive when the routine triggers correctly, and not arrive when the routine fails to trigger. This tells you whether the trigger is the issue or the action.
The audit habit that catches silent regressions
Once a quarter, run each of your important Alexa routines manually from the app and confirm the actions still execute correctly. Voice ecosystems update silently and sometimes deprecate features that your routine depended on. You discover this only when you try the routine.
This takes fifteen minutes for a typical household. Note any routine that runs partially or not at all, and rebuild affected actions while context is fresh. The wider topic of cloud-side changes breaking previously-stable automations is in our routine recovery guide.
