possible username conflict

Hi

I am using rules views integration 1.x dev that I downloaded July 21st, 2010
Views 6x-2.11
flag 6x-1.3
path-redirect 6x-1.0.b7
pathauto 8x-1.5
global redirect 6x-1.2

I use rules-views to run a periodic view weekly. The view selects a set of nodes then the executor uses a rule to add global flags to the selected nodes.

This was working for me until this week.

I am the admin, and until this week my userid was dpatte
I changed my userid this week to dpatte-editor, without any problems

Today when i manually ran the periodic view, I got a whole pile of warnings that i never got before.

autogenerated alias user/dpatte conflicted with an existing alias.
created new alias user/dpatte-0 for user/3700
(it then did the same for blog/dpatte and feed aliases as well)

autogenerated alias user/dpatte conflicted with an existing alias.
created new alias user/dpatte-0 for user/3701
(it then did the same for blog/dpatte and feed aliases as well)

autogenerated alias user/dpatte conflicted with an existing alias.
created new alias user/dpatte-0 for user/3702
(it then did the same for blog/dpatte and feed aliases as well)

etc.

it did this for each node that the view had selected.

the thing is that since i changed my userid, i no longer have a user/dpatte, i have a user/dpatte-editor though. My username change this past week created a redirect from user/dpatte to user/1 and an alias from user/dpatte-editor to user/1

One of the modules that is being used for this manual periodic view seems to be getting my username mixed up when the periodic view is run.

Its as if something is taking my current username (dpatte-editor) but truncating it to (dpatte) before using it in the executor, then trying to create a user dpatte to run the view. Since I already have a redirect from user/dpatte, it generates the above warnings and renames the executor user to dpatte-0. Is this possible?

One extra side effect is that in my database, I have noticed that my autoincrement for next user # has jumped up dramatically. Maybe its being incremented once for each node that is processed in this process?

Thanks

BTW - the view still worked, but produced hundreds of warnings. Since the warnings where about deleting hundreds of users and renaming hundreds of aliases, i nearly had a heart attack till i figured out what was going on :)