Conversational was updated to "optimize" the gcode and save unnecessary moves, like when facing and then outside chamfer with the same tool. It does this by commenting out the spindle shutdown and coolant off commands (M5, M9) and then commenting out the G30.
If you manually edit the code to add a tool change before the next ops M1 (for applying tapping fluid, for instance), and THEN re-edit anything in conversational, it will "optimize" the M5, M9, and G30 right above the tool change.
I recommend you open your code in gedit, search for "T0" and make double sure there is a G30 right above it, unless the sequential operations share the same tool and you are okay with the optimization.
I've shared this with the FB group and wanted to make sure it got out to as many people as possible.