Overdue cards, tagged to be Reviewed, show up for Review AGAIN right after the LAST card was rev'd.

[Vit]

     Overdue cards, tagged to be Reviewed today, show up for Review AGAIN,  right after the LAST card was reviewed. 
In the past, I had been dismissing this phenomenon....
I'd just stop review -- if I noticed it on time { 40% chance that I did not }.

     I decided to see what damage would the second review do; I rated the card 5;
another tagged card ( reviewed today ) shown up, too. I aborted the process and
opened the Browser; 
the card I reviewed second time,  the Next Interval was advanced by 1 day.

I suspect the  negative 'side effect' of this  -- it adds another Review Rep, thus affecting the Next Interval ( making it longer ? ).

I think the culprit are Tags; as you can see on the screen shot, the counter shows 18 cards ACTIVE.
    
     This is a low priority for me - bcs I am aware of it.
  Curious if other users experienced this.

Vit

[Peter Bienstman]

Please mail me your database privately and tell me which card has the problem.

Peter

Vit <vrem2003-...@yahoo.com> wrote:

     Overdue cards, tagged to be Reviewed today, show up for Review AGAIN,  right after the LAST card was reviewed. 
In the past, I had been dismissing this phenomenon....
I'd just stop review -- if I noticed it on time { 40% chance that I did not }.

     I decided to see what damage would the second review do; I rated the card 5;
another tagged card ( reviewed today ) shown up, too. I aborted the process and
opened the Browser; 
the card I reviewed second time,  the Next Interval was advanced by 1 day.

I suspect the  negative 'side effect' of this  -- it adds another Review Rep, thus affecting the Next Interval ( making it longer ? ).

I think the culprit are Tags; as you can see on the screen shot, the counter shows 18 cards ACTIVE.
    

   &n bsp; This is a low priority for me - bcs I am aware of it.

[Peter Bienstman]

Hi,

According to the database you sent me, that card was last reviewed May 29 and is scheduled for next review Jun 11th.

That you see it a second time on May 29 is either because you review ahead of schedule and/or you have 3rd party plugins installed which disturb Mnemosyne's scheduler. (I see from the screenshot you sent me that you have lots of them installed).

I also manually fixed your database regarding the tag '17' and manually deleted that tag (new version attached). The problem is unrelated to scheduling, but rather comes from the fact that people can add tags like '::17' (i.e. without a parent tag) that confuses the tree display algorithm. I will make sure people cannot create such tags in the next version.

Thanks!

Peter