Changing the title on Hudson Valley throws an error

[absempere]

Alysa tried to update the Hudson Valley title to "Culture Cartography" and got an error. I logged in via the shared Performant account and got this error:

When I clicked the "About the Project" link again, I saw the original title and was still logged in.

[ajolipa]

Huh, I just tried to reproduce and instead it worked? So the good news is the title is changed, the bad news is I'm not sure what went wrong before. I do see some errors in the Netlify function logs which as best I can tell are some sort of connection error or timeout error with the MongoDB database attached to Tina, but I can't tell exactly what went wrong. @dleadbetter might have insights, since he set up the self-hosted Tina stuff?

Jan 6, 05:40:04 PM: 51215c6c ERROR  Unhandled Promise Rejection 	{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"MongoServerSelectionError: Server selection timed out after 30000 ms","reason":{"errorType":"MongoServerSelectionError","errorMessage":"Server selection timed out after 30000 ms","reason":{"type":"ReplicaSetNoPrimary","servers":{"tinacms-13b16b6b.mongo.ondigitalocean.com:27017":{"address":"tinacms-13b16b6b.mongo.ondigitalocean.com:27017","type":"Unknown","hosts":[],"passives":[],"arbiters":[],"tags":{},"minWireVersion":0,"maxWireVersion":0,"roundTripTime":-1,"minRoundTripTime":0,"lastUpdateTime":1165165,"lastWriteDate":0,"error":null,"topologyVersion":null,"setName":null,"setVersion":null,"electionId":null,"logicalSessionTimeoutMinutes":null,"primary":null,"me":null,"$clusterTime":null}},"stale":false,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"setName":"tinacms","maxElectionId":null,"maxSetVersion":null,"commonWireVersion":0,"logicalSessionTimeoutMinutes":null},"stack":["MongoServerSelectionError: Server selection timed out after 30000 ms","    at _Topology.selectServer (/var/task/netlify/functions/tina.js:469641:34)","    at async _Topology._connect (/var/task/netlify/functions/tina.js:469541:26)","    at async _Topology.connect (/var/task/netlify/functions/tina.js:469505:11)","    at async topologyConnect (/var/task/netlify/functions/tina.js:470121:13)","    at async MongoClient2._connect (/var/task/netlify/functions/tina.js:470132:11)","    at async MongoClient2.connect (/var/task/netlify/functions/tina.js:470065:11)","    at async MongodbLevel._open (/var/task/netlify/functions/tina.js:534335:5)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: MongoServerSelectionError: Server selection timed out after 30000 ms","    at process.<anonymous> (file:///var/runtime/index.mjs:1276:17)","    at process.emit (node:events:517:28)","    at emit (node:internal/process/promises:149:20)","    at processPromiseRejections (node:internal/process/promises:283:27)","    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)"]}
Jan 6, 05:40:04 PM: 51215c6c ERROR  [ERROR] [1736203204868] LAMBDA_RUNTIME Failed to post handler success response. Http response code: 400.
Jan 6, 05:40:04 PM: 51215c6c ERROR  RequestId: 51215c6c-6023-4c7b-b938-b2189cedd251 Error: Runtime exited with error: exit status 128
Jan 6, 05:40:04 PM: 51215c6c ERROR  Runtime.ExitError

[dleadbetter]

Hmm, not sure, I haven't seen this one before. Possibly an issue with the MongoDB cluster on Digital Ocean. Are any users still able to replicate the issue?