OK here is the test:
Manually write data to database
Click Test
I click Test Few More
Manually write data to database (Reset To 0 and 100)
Click Test
Before I was using Increase but I was told to use Update instead.
Increase is different:
The function is supposed to read itself the db, while in Update we give that function the value we think we read from DB.
I also had problem (not exactely the same, I had soemtimes 3 times the same number) but that problem was maybe related to TAG and not Update Program Setting with Increase.
Good test. Looks like Update Type:Increase is broken. Looks like it is cached, and not read from DB.
What syntax are you using? {:X}, or {SETTING:X}, or {GLOBAL SETTING:X} ?
Nice test.
However I have it wrong with Update also using {GLOBAL SETTING:UpdateType}
Could you try?
Using {SETTING:X}
can you try with GLOBAL?
Unbelievable we got another bug `{GLOBAL SETTING:X}’ = {:X}. So, change it back to {SETTING:X} You should be fine now.
EDIT: GLOBAL read from cache in “Before” but read from database in “After”. It seem it doesn’t know the value was update (I manually change database) so, it use local value but after Update Program Setting Action it read from database. @QMcKay
actually I have it setup now with Update and I give the {REPORT SQL} value.
I haven’t had double today, I think I will stick with it until the patch.
168 posts later and we uncovered 2 bugs. LOL.
Good work Team! 
was this fixed as im getting same issue.
Mine is set to {GLOBAL SETTING:ORDERNUMBER}
What shall i change it to?
