Why do routines stop working after an update?
Because a routine depends on permissions and capabilities that a platform can narrow, and updates narrow them regularly. The tag is unchanged and still reads perfectly, which is why the tag is the last place to look and the first place people do.
What a routine depends on
An automation application being allowed to run in the background. A set of permissions it was granted. Access to actions the platform exposes. Sometimes an account with a service.
Every one of those is granted by the platform and can be narrowed by the platform.
The tag depends on none of it. It holds bytes and hands them over, which is why it is the one component that never breaks this way.
What updates take away
Background permission, which is tightened repeatedly and quietly, usually in the name of battery life.
Permissions that are reset and must be granted again, which nobody is prompted to do.
Actions that are removed or now require confirmation, which turns a silent routine into one that asks.
On Android, the right to receive tags at all. From Android 16, the first tag an automation application receives brings a notification that lets the user stop it receiving tags, and from Android 17 a force stopped application receives none until it is opened again, as the NFC basics guide describes.
And manufacturer automation layers that change independently of the platform, on their own schedule.
Apart from that one notification, none of these announces itself. The routine simply stops, and no message explains why.
Diagnosing it
Read the tag first, which takes seconds and eliminates the component people suspect. It will be fine.
Run the routine manually from the automation application. If it fails there, the problem is a step rather than the trigger.
If it runs manually and not from the tag, the trigger is being blocked, which is usually background permission. On Android 16 and later, also look under Settings > Apps > Special app access > Launch via NFC.
Check permissions and battery restrictions for the automation application, which is where the answer sits most of the time.
Building something more resilient
Fewer steps, since each one is a dependency that can be withdrawn.
Prefer actions the platform is unlikely to restrict, which usually means opening something rather than changing something.
Where the steps are home devices, put them in a scene in the home system rather than in a phone chain, since the system is a more stable host.
And write down what each routine does, so rebuilding after an update is a task rather than an archaeology exercise.
Frequently asked questions
Did the update break my tag?
No. A tag holds bytes and hands them over, and no update changes that. Read it first to eliminate it in seconds.
Why did it stop with no message?
Background permissions and action availability are narrowed silently. Nothing prompts you when a routine loses what it needed.
How do I find the cause?
Run the routine manually. Working manually and failing from the tag points at the trigger being blocked, usually by background restrictions, or on Android 16 and later by the application having been refused tags.
How do I make routines last?
Fewer steps, actions unlikely to be restricted, and home device steps kept in the home system rather than the phone.