Proc caching in irules? It is driving me crazy

It looks like there is some kind of unpredictable caching with proc's in irules.

 

I am using a local proc in a single irule and I have found that while debugging an irule it seems like some changes to the proc don't take effect. Log commands are one thing among other select statements/command I have had problems with.

 

I wasn't sure, but then after coming to my wit's end I just copy/pasted the proc into a second proc in the same irule and just added a character on the end of the proc name and all of a sudden the log commands are working if I call the renamed proc

 

Before renaming the proc in the irule, i tried unassigning the irule to the vs and reassinging,obviously updating/saving the irule, but nothing worked. The proc rename worked and I would guess an irule rename would work as well as a workaround

 

Has anyone else had this bizarre mind numbing experiencing with procs? Is this by design and it is just not published/documented?

 

Is there anyway to clear this caching when debugging irules/procs?

 

Thanks Matt