There was an issue where tasks stored in the Room database were not inserted in a specific order and a conditional task could sometimes be inserted before its parent task existed in the database. This caused Room to skip inserting the associated conditional constraints, since the required foreign key was not yet present.
This issue was fixed in PR #3383. However, users who already encountered this problem will continue to see it, because Room has already stored the conditional tasks incorrectly