Hi @maybellyne I wanted to give my latest update on the issue: it appears that it was resolved. The web host support identified the cache settings as the possible root cause for the 502 errors. Apparently, it was disabled or it was being refreshed too often. They changed these settings and now it’s working correctly.
Thanks for your support!