Downlink message timeout

ChirpStack Application Server
1

I hae a device that sleeps for a set time then wakesd up, sends its data and goes back to sleep.
I can send a message to change the timing. this works fine if the cycle time is only 10 minutes but if i set it to an hour even thought the downlink message is set to confirmed it vanishes and for some reason never gets to the end device.

Is there any form of timout setting that needs to be adjusted for this?

2

Nope, the downlink should stayed queued forever, unless acted upon.

3

Thanks @bconway. Seems to have sorted itself out so not sure why it was doing that. Putting it down to user error :slight_smile: