Anyone been having issues with transactions just failing to save for no good reason? I've had instances of CSV imports and Map/Reduce scripts the last several months throwing the fun "unexpected error" for no reason I can figure out. NS wasn't down during that time and rerunning these processes without any changes lets the transactions go through fine, so it's not an issue with the original data submitted. This has happened before and after 2024.1. It's annoying because a couple records failing causes a whole larger batch process to fail. I realize we could (maybe should) build in redundancy or modify it so it doesn't fail the whole batch, but seems stupid we'd have to modify this process to account for NS records randomly not saving on occasion for no reason.