Delay in Persistent Variables Writing to Logger database

[Br3ndaMca]

Hi

I have persistent user variables that are updated via an admin script.  The admin script is set to refresh every 15 seconds.  I can see the values update in real time in monitor mode on the admin script but when I check against the database the values don't update for a long time after (sometimes over 5 minutes or more).  If I run the rttest command to show the value the router currently stores this also sometimes does not tally with the database.  Has anyone else experienced this or know what is the cause?

Thanks

Brenda

[bill.king1]

I have not. This may seem like a silly question, but are you certain that you're not overwriting the values for that variable in another admin or even routing script? Some people get confused as to the use of a persistent variable vs. the Peripheral Variables for instance.

And just to clarify, you're saying that you see it update in the script and rttest show the same value, but the database doesn't, correct? This could also just be a case where the data being written to the database is lagging due to other activity (purging, heavy traffic, reports, etc.). If you look at the database time for one of the other tables like Route Call Detail or Termination Call Detail, is the date/time stamp pretty close to current time?

[Br3ndaMca]

Hi Bill

It's all new variables and the only other place they are being used is reading the value of them in IF nodes in a routing script.  It's a pre-prod environment so there is no real load on it bar UAT team running tests.  Yes rttest is showing the value as per the admin script and the database will eventually update just not in real time.  Any idea what logs I could even look at to troubleshoot?

Thanks

Brenda

[bill.king1]

I guess the question is, does it really matter? If rttest is showing the correct value, then using/calling on those variables value in a routing script should be fine. Are you saying that isn't the case?

So variable A is set to Open at 9am in your admin script assuming it runs every minute for instance. You do a call at 901am where you have an IF node that checks variable A's value to see if it is Open or not, and then route accordingly.

[geoff]

I agree with Bill. In fact, I never make user variables persistent as I think it's a waste of processing power. Why write them to the DB? The only use of this is on a Router failure and restart. But what's the point? The Admin script fires and sets them.

PS: every 15s is a bit too often, in my opinion. Every minute is about as tight as I ever go.

Regards,
Geoff