The next time this happens I’ll be ready to properly debug it, as I’ll have the raw JSON received (with timestamps). I’ll recreate the case like I did to debug the context
issue.
@devnull @how @trwnh Ok, I finally had the time to recreate this case in a spec. The reason this happened is because: Discourse was unable to resolve a Conversation type for context. The error thrown in 1 was too nested to properly roll back the relevant transactions. This will address the immediate issue @devnull I haven’t been keeping up with the latest on context / collections etc. Could you briefly explain the thinking behind using “Conversation” instead of “OrderedCollection” in c…