What happens if a Basic Rule executes a "send a notification" action but the LAN router is down?
Is it queued until the connection comes back, or blasted into the void?
What happens if a Basic Rule executes a "send a notification" action but the LAN router is down?
Is it queued until the connection comes back, or blasted into the void?
Depends on the driver that you are using for the notification device. In general, it will probably just eventually time out on the HTTP request responsible for sending the notification, again depending on the driver, but likely after a 10-second default or whatever the developer specified, up to 300 seconds.
The built-in mobile app driver looks a bit different; I think everything is queued and should happen upon reconnection as long as that queue isn't cleared by a hub restart, or perhaps something else I'm not seeing with a quick glance (which is all the familiarity I have with that
).
But it is ultimately dependent on the notification device, not the app -- the app just calls the command on the device, the same way you could from its device detail page for testing, for example.
Thanks! I'll try it and see.