(502): Bad Gateway

Hi @Kal_Lam , we are facing a bad gateway error from like 3 weeks now. When tried the with api link multiple times, dataset can be downloaded with multiple tries. But since these datasets have been connected with pbi dashboards, dashboards fails to refresh due to this.

Summary

Hi @Kal_Lam ,
There is a recent 502: Bad gateway exception from the kobo in the data export. But when I try with the API link multiple times, it will eventually get downloaded. But since we have connected these datasets with dashboards, this error prompts to refresh fails.

@viraj_hapuvita, are you linking your data to Power BI?

@viraj_hapuvita, pinging @osmanburcu, our Power BI expert for your support here.

1 Like

Yes. I have connected using API link

Hi @viraj_hapuvita, I would like to ask how big your data size is? how many rows? how many columns? This error might happen time to time due to size of the data. I also tested the Save the children’s kobo server and couldn’t see any problem (I am also a Save the children staff). You can reach me though teams if needed.

error usually indicates an issue with the server communication, where one server acting as a gateway or proxy receives an invalid response from an upstream server. In your case, the error might stem from the KoBoToolbox server when attempting to export data, leading to inconsistent availability of the export.

Here are some steps you can take to address this:

1. Check KoBoToolbox Server Status:

  • Sometimes, the 502 error is caused by server-side issues. Visit the KoBoToolbox Status Page to check for any reported outages or maintenance.

2. Automate API Retry Logic:

  • Since the API works intermittently, you can implement a retry logic in your system when fetching the data using the API. This means that if the request fails, the system will automatically retry the request after a certain delay. You can set a maximum number of retries to avoid endless looping.