We are encountering this issue after deployment. It works fine in the local environment. Although the issue does not occur every time, it happens most of the time. I'm sending you the mail with logs.
