Hey @dortega5185 , apologies for the delay replying to you on this, we missed your question when it was first posted!
First, I would recommend updating your Next.js plugin to at least version 4.18.0 (see this announcement post for more details). That won’t necessarily fix the behavior you’re seeing, but I would definitely recommend this as a first step.
Regarding the error you’re seeing, the engineering team is already looking into this as of now, and we’ll follow up on this thread as soon as we have more information!