The issue has been fully resolved. After investigation, we determined the root cause was a missing environment variable that was not included during the deployment process. That configuration has now been added and validated, and the affected functionality is operating as expected.
We are also strengthening our internal review and release validation processes to ensure required environment configuration is consistently verified prior to deployment. These additional checks are intended to reduce the risk of similar issues occurring in the future and improve the overall reliability of our release process.
