web-UI mistakenly shows workflow as COMPLETED in case there are issues with search attribute upsert-ion from server's end

Describe the bug
If there is any error in temporal server while upserting search attribute - webUI mistakenly shows the workflow as COMPLETED while we are inside it, wherease from outside i.e. main workflows list page - it is shown correctly i.e. still in RUNNING state

To Reproduce
Steps to reproduce the behavior:

1. upsert a stringified json as a value using operator service into a search attribute of type IndexedValueType.INDEXED_VALUE_TYPE_TEXT
2. this will likely generate an error on temporal server: "error":"pq: syntax error in tsvector:
3. goto webUI and track the concerned workflow with its relevant workflowID
4. Click on the workflow - inside it will show that it's COMPLETED
5. navigate out to main workflows listing page - there it is still aptly shown as - RUNNING

Expected behavior
There should not be a mis-match between workflow status inside and outside i.e. on its own event history page and on workflows listing page

Screenshots

Desktop (please complete the following information):

• OS: macOS
• Browser: brave
• Version : not sure

Additional context
We should also look into why temporal server is not able to upsert stringfied json into search attributes which are of TEXT type

No files or tests are named. Start by reproducing the mismatch using the listed search-attribute upsert failure, then compare the workflow detail event-history status with the main workflows listing status. Done means both views consistently show the workflow as RUNNING when the server-side upsert error occurs.