This will be fixed in 1.4.6.
The suggested question mechanism is jury-rigged on top of the post drafting mechanism which is entangled with the question editor delegate, so when the question editor navigates to a suggested question it attached the question as its editing delegate. We had one method,
questionEditorViewController(_:,didPostQuestionWithResponse:) that different delegates handled differently, and the question view controller simply replaced the displayed question with the new one because it assumed it was an edit.
Now the question editor still attached the delegate for drafting purposes but when it submits a new question or requests a suggested question, it universally does this as a notification to the root view controller. It was already doing this in some circumstances and this is the standard behavior used by the hot network question today extension, Spotlight, the browser top bar, etc, so it should be more reliable and reduce the number of inconsistencies we have.
I'm hoping to significantly improve drafting by the final App Store release so we can get rid of delegate reassignment altogether.