That reddit post you linked describes what is likely the problem very well. The a transaction at the current block number will cause the contract to throw an exception. I don't think parity is smart enough to know that you're scheduling the transaction for a future block number when it checks this.