Traces keeps getting disabled
Hi,
Since the last update regarding Traces (where a few new options was added) we have expirenced quite a frustration thing, it keeps disabling, alot.
Without the script crashing, it usually can run 1 to 3 times, and then its set to disabled, and this can be within secounds or minutes.
It can be as simple scripts that changes the title, run the script 2 times with the exact same data and it gets disabled after the 2nd time
Anyone experience the same thing? and most importantly, is there anyway to force it not to be set to disabled?
Regards
Pär
All Replies (2)
Hi Par,
I am not 100 % sure, but in my experience it seems that "old traces" have this issue more often than newly created ones. So what I often do is: delete the existing trace and create a new one. Then it does not happen (but I am not 100 % sure it never happens).
I can confirm that this issue happens occassionally.
As Bas says, there is a limit on 100 traces in the log. It will disable it self if you exceed this limit. So you will have to delete the old traces.