1.6.7 osx scheduled transaction stuck at "SUBMITTING"

[Yuripetusko]

Was going to participate in ICO today, created scheduled transaction but it was stuck at Submitting and there's no way to cancel it. ICO is over and it's still there :)

Also maybe unrelated but I see Parity//v1.6.7-beta-e128418-20170518/x86_64-macos/rustc1.17.0 Unknown capability at bottom left corner

[ghost]

Hi,
BAT ICO didn't start yet. It starts at 3,798,640 block exactly as you scheduled.
Use "WHEN ARE WE THERE" dapp form Parity applications tab to find out what time this block takes place approximately.

[Yuripetusko]

@johnerfx it wasn't BAT but Mysterium ICO, it was at 13:00 today and I did time scheduling, I think yo ucan see a small part of my other transaction that is scheduled for BAT, please ignore it

[ghost]

Yes, you are right, my bad.

[tomusdrw]

If you have a scheduled transaction from an account every other transaction you'll try to send from that particular account will run only after the first one was executed.
So the transaction you scheduled for BAT is blocking each subsequent transaction.

You can cancel BOTH of the transactions by running once with parity --no-persistent-txqueue flag or using this config file:
https://paritytech.github.io/parity-config-generator/#config=eyJtaW5pbmciOnsibm9fcGVyc2lzdGVudF90eHF1ZXVlIjp0cnVlfSwiX19pbnRlcm5hbCI6eyJwbGF0Zm9ybSI6Ik1hYyBPUyJ9fQ==

And restarting Parity (remove the config file afterwards)

[Yuripetusko]

@tomusdrw this is it! I wish I knew about it before Mysterium ICO finished :) but alteast I will be prepared for next one. Thank you

[thebalaa]

This seems like a bug at worst and bad UX at best.

[tomusdrw]

@thebalaa This is a technical limitation, transaction has a fixed nonce (order) that needs to be defined at the moment of signing.
I agree that UI should be more informative about this limitation.

[Yuripetusko]

Would be nice to have ability to cancel transactions that are in queue. At the moment it is not possible

[tomusdrw]

The PR is pending #5716