When checking off a task with a recurring due date like !(2020-07-08 | ~4d) in the web interface or app, Dynalist will immediately create a new task with the next due date (or modify the task, depending on user preferences).
This does not work (perhaps obviously) when using the API to mark that same task as done. Now new task will be created (or modification made).
Is this a known and accepted limitation of the API? I can imagine that recreating the same logic serverside may bring its own challenges.
If this is the case then perhaps a note could be added to the API docs, since the system does not work as advertised (for the GUI).
Or if somebody has a trick to share, I’d be very happy to hear it.