I found it strange why I get back to run mode by clicking on the stop message.
Because one of the recent platform updates changed the field with the Siglent Logo, Trigger State and Trigger Frequency Counter, which was not clickable before, to the "force Trigger" button, that some people had requested.
Generally, whenever the DSO waits for a trigger - or processes a trigger, it has to be in Run mode. With Single Trigger, the scope is in Run all the time, until the trigger event finally occurs and stops the acquisition.
In Stop mode, the scope ignores trigger events via the usual sources (channels, ext, line), but if you click on the "
Force Trigger" field, you also
force the scope to process an (artificial) trigger event, hence it
has to switch to Run mode.