No, and as of v0.0.63 the app stops you.
Two runs drive the same browser and interleave, and the damage used to be silent: both runs reported success while each partly overwrote the other's work. Measured directly — two concurrent runs each set a marker and each read the other's back, both reporting ok: true.
A second run on a profile that is already busy is now refused, naming the profile. Runs on different profiles are unaffected, and a schedule listing the same profile twice has always deduplicated it.
Two runs drive the same browser and interleave, and the damage used to be silent: both runs reported success while each partly overwrote the other's work. Measured directly — two concurrent runs each set a marker and each read the other's back, both reporting ok: true.
A second run on a profile that is already busy is now refused, naming the profile. Runs on different profiles are unaffected, and a schedule listing the same profile twice has always deduplicated it.