The behaviour is that repeating spends are added and marked as repeating in the log.
Each time the log is played, any repeating transactions are repeated accordingly and added to the log (as normal transactions) leaving the last such transaction as a repeating transaction. This last transaction is always a delayed transaction which means that the projected envelope value will include one future payment of each recurring transaction.
By deleting the future transaction, the repeating transaction is deleted as only the future transaction is marked as repeating in the db.
NOTE: There is a known bug that the playlog function is only called on creating of activity, so for the next projected spend of a recurring payment to appear, the activity needs to be restarted.
notriddle
commented
8 years ago
The behaviour is that repeating spends are added and marked as repeating in the log. Each time the log is played, any repeating transactions are repeated accordingly and added to the log (as normal transactions) leaving the last such transaction as a repeating transaction. This last transaction is always a delayed transaction which means that the projected envelope value will include one future payment of each recurring transaction. By deleting the future transaction, the repeating transaction is deleted as only the future transaction is marked as repeating in the db.
NOTE: There is a known bug that the playlog function is only called on creating of activity, so for the next projected spend of a recurring payment to appear, the activity needs to be restarted.