Hi @Giridhar.Prabhu,
I’ve encountered this type of behavior in the past, but prior to the new Quick release so may be a broader bug that takes place from time to time. In the past, I received the same thing where I got that message, closed out and then the field was created and operational. Almost like it didn’t close when creating and then the error message pops up because it’s already been created.
The behavior was never permanent though and went back to normal after a short time; is this something you’ve been receiving often or just on occasion?
What type of calculation were you attempting to make/how complex was the syntax?
I would also suggest creating a support ticket to report this bug taking place if haven’t already!
Hi @Giridhar.Prabhu,
Thank you for letting us know. As Brett mentioned, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!