I just saw your post is tagged with SuiteCommerce Advanced. We are on SuiteCommerce Standard. We didn't change anything, so I'm guessing either Netsuite did an update that fixed it or maybe an automatic script ran that fixed it? I wish I could be of more help, hopefully they can help via your Support Case.

@Arun Reddy12 Ours started working again this morning. They must have fixed it somehow. Hope yours is fixed too!

Hi @Arun Reddy12 , did they fix this for you? I believe we're experiencing the same problem. We followed the steps in that SuiteAnswer as well (https://suiteanswers.custhelp.com/app/answers/detail/a_id/90060/loc/en_us) and still getting this error. @Richard James Uri-Oracle : Can we get assigned to the ongoing defect to be…

Filed a case. Hopefully everything comes back online soon. Thank you.

Cloudflare, and it looks like we're back online too.

Same here, same error

Same here. Trying to get in contact with our rep.

Hi Chase, What parameters do you have for the Saved Search that compares intervals of customer's orders? (if you still have it) Thank you!

Was this fixed? We haven't been moved to 2019.1 yet, but it's coming soon. We're looking to setup a Branded Checkout Domain sometime soon as well. rnedelkow ?

We're down too rnedelkow Looking forward to the fix, thank you.

Not sure if you're using standard checkout and still need a solution, but this thread may help: https://usergroup.netsuite.com/users/forum/general/latest-release/version-2016-release-2/416018-2016-2-how-to-make-the-phone-number-field-required-manditory-during-web-store-checkout-or-registration See nugkent's comment on the…