According to the user guide:
Profile: Select which equipment profile to utilize when starting Ekos. If Ekos & INDI are already started and online, this selection is ignored.

Tonight I had 2 crashes in a row starting a Scheduler job that had the profile set to my usual profile by name instead of Default. Ekos was already connected and I saw the log window reporting an attempt to connect devices for the profile nevertheless. After that, KStars crashed. This happened twice.

Only setting the profile in the job to Default I could start. Looks like the selection might not be ignored when ekos is already connected?

I tried to reproduce it with simulators, but at least with those it works fine. Could you please post your scheduler and sequence file and ideally also the log files?

Sorry for the delay. The issue appears intermittent, as previous sessions had the profile explicitly selected and did not crash. Here are the scheduler and sequence files. I did not have file logging enabled unfortunately.