Downlink commands not getting processed in chirpstack V4

1

Hi,

We are facing issue while sending downlink command to device, that command not getting processed. it’s been stuck in enqueue itself. I can see the record is present in DB.

In Chirpstack log we are seeing below error messages.

2023-02-21T15:36:12.917612Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:14.927187Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:16.935540Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:18.944562Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:20.953780Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:22.962816Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:24.972130Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:26.980222Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:28.988496Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:30.997831Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS
2023-02-21T15:36:33.016615Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=region_name does not exist in REGIONS

Could you please help me to resolving the issue. We are not getting exactly what causing the this issue.

Thanks,
Venkat.

2

This looks like you have selected a region in the device-profile which is not enabled in chirpstack.toml.

3

I have selected the correct region only, Same device profile assigned two devices and one device working fine able to send downlink commands but other devices downlink not going and in the logs we are able to see above error messages.

Thanks,
Venkat.

4

We are seeing above error log messages, after below logs messages.

2023-03-07T13:09:41.282750Z INFO gRPC{uri=/api.DeviceService/GetQueue}: chirpstack::api: Finished processing request status=“200” latency=1.509263ms
2023-03-07T13:09:41.798926Z INFO chirpstack::gateway::backend::mqtt: Message received from gateway region_name=“in865” topic=“in865/gateway/506f980000000106/event/up” qos=0 json=false
2023-03-07T13:09:41.935221Z INFO chirpstack::storage::device: Aquiring device lock dev_eui=506f980000003291
2023-03-07T13:09:41.935748Z ERROR chirpstack::downlink::scheduler: Schedule next queue-item for device failed error=Get device lock