Our writers are reporting that they are seeing āsearch timeoutā errors on a regular basis. They report seeing these errors when creating a new record or editing an existing record in our āofferā model. Iām assuming the āsearch timeoutā comes from dropdown fields that are single-linked fields to other models.
(Recommended) Whatās the URL of the record or model in question?
Model is āofferā. Seems to be random. Iāve had it happen for me once, but Iām rarely in those forms. They are in those forms all day, though. So, I would expect they would see a lot more than me.
Iām assuming this is a volume problem. Some of our fields are referencing models that have a lot of records. But, I just wanted to put this out there and at least make you guys aware of the problem.
We fixed one specific edge case bug we discovered that was affecting single-linked fields accidentally causing timeouts on certain types of typing (basically, we werenāt correctly trimming edited text fields, and sometimes that led to blanks searches that automatically time out).
I canāt tell (from the limited information) whether that was directly the cause of this particular incident. But please let your editors know that weāve made an improvement. If it keeps happening, please keep reporting itā¦ any screenshots, console errors, or (best of all, if they know how to use it) captured failing network requests will help a lot.
Iām also trying to get that āError ID: [object Promise]ā fixed for you so that the error ID will show up properly (sorry, that got missed during the merge). Those IDs are serverside reports that help us track issues like this downā¦ it would be more useful if you could actually see it, of course
