This is very strange and might not be a bug but due to my limited knowledge of how effects work...
I have 2 simple kick drum patterns using track 7, both set to break/jump at step 0F (16 steps). They are connected in an island and play one after another. No other patterns, effects or anything else.
I added a Retrig step/repeat effect to step 05 of pattern 2 set to 0016 - great, I have a nice ratchet effect.
Then I added Probability FX1 % to step 04 of the same pattern and set it to 0032, expecting the ratchet to work 50% of the time...
The result was that both patterns have now lost their break/jump values and play all 64 steps each
(the break / jumps are both still there on step 0F in each pattern but they don't work anymore).
Stopping and starting, deleting the probability or deleting the retrigger effect makes no difference - the patterns are now stuck at 64 steps long. The only way to solve this was to make new patterns or restart the nerdseq.
I thought it might be because I was using an earlier firmware version so I just updated to 1.20 RC3 but had the same result.
Assuming my method is correct I assume this is a bug and not meant to happen?
I have 2 simple kick drum patterns using track 7, both set to break/jump at step 0F (16 steps). They are connected in an island and play one after another. No other patterns, effects or anything else.
I added a Retrig step/repeat effect to step 05 of pattern 2 set to 0016 - great, I have a nice ratchet effect.
Then I added Probability FX1 % to step 04 of the same pattern and set it to 0032, expecting the ratchet to work 50% of the time...
The result was that both patterns have now lost their break/jump values and play all 64 steps each

(the break / jumps are both still there on step 0F in each pattern but they don't work anymore).
Stopping and starting, deleting the probability or deleting the retrigger effect makes no difference - the patterns are now stuck at 64 steps long. The only way to solve this was to make new patterns or restart the nerdseq.
I thought it might be because I was using an earlier firmware version so I just updated to 1.20 RC3 but had the same result.
Assuming my method is correct I assume this is a bug and not meant to happen?

