I have a trigger on the base table of one of my feature services. After Insert seems to work fine as I have concluded that a Survey123 to FS transaction does a Input, then an Update.
After Insert statements to not cause the Code 500 Error.
After Update does cause the Code 500 error, but not everytime, most of the time.
Is there a rational reason for this where I can code around it. I need to pull data from insert after an update without the code 500.
I should add that the trigger performs fine and correctly when making the edits right in ArcMap, every time. Also I have never had these issues with Collector (however most of my Collector FS is versioned, Survey123 is archive enabled.