@Craig Haroldson When this happened months ago, they told us that it was due to them improperly casting the id as scientific notation and their solution was for us to convert the id to a string.

First of all, that's wild. 😳 Our issue may be different, though, since it's intermittent... typically less than 1 out of 100 calls to submitFields in one particular area/record fails. Today, however, we had a string of 10 with a 30-40% failure rate.

We are having the same issue and that's how it was before as well. It seems like it's completely random when it fails and they come in batches and across multiple different scripts.

Curious if you're using SuiteQL queries? We're also seeing random UNEXPECTED_ERRORS on query.runSuiteQL and working around those using a retry hack.

We have one process that creates records from a custom record with a payload. The custom record has a status list that we update when it's done via submitFields. It has succeeded 255 times and failed 32 times to update this status.

Same exact situation... custom record, updating status via submitFields. Wild.

I haven't seen it on the query module yet, but we do have quite a few queries.

We've been assigned to existing Defect 757740 as a U3. Curious if you're the originator for 757740?

We have 719797 and 745571 from previously for this issue, but they closed both after our workarounds from casting to the id's to strings. We haven't gotten a defect for the current version yet.

We're still seeing some random UNEXPECTED_ERRORs, but not in the one particular place that we had been seeing it frequently.

We are still seeing them randomly too. It most seems to be on custom records. They won't really give us an answer

I haven't heard any more on the defect, so guessing it's not moved much/at all.