The timeout for calls against the ChirpStack application server has been increased from 3 seconds to 30 seconds.
This should fix the issue with organizations showing inconsistently in the gateway list. The issue occurs when the API requested data for multiple gateways from the ChirpStack application server REST API and the calls time out before the Application Server can respond.
I suspect multiple other frontend-issues are related to this. We will look into optimizing the access while fixing these other issues.
The timeout for calls against the ChirpStack application server has been increased from 3 seconds to 30 seconds.
This should fix the issue with organizations showing inconsistently in the gateway list. The issue occurs when the API requested data for multiple gateways from the ChirpStack application server REST API and the calls time out before the Application Server can respond.
I suspect multiple other frontend-issues are related to this. We will look into optimizing the access while fixing these other issues.
Fixes OS2iot/Os2IoT-frontend#45