Hi @jthi .
It happens when an AddIn is updated.
One possible root cause:
I use UpdateCheck.jsl from Add-In Manager, triggered via AddInLoad.jsl *)
In general, it works quite smooth, but sometimes an AddIn is disabled after a "patch day".
In the AddIn Manager manual I found:
However, as of JMP 13, using this script within an addinLoad.jsl script will not work.
Fortunately, with newer Jmp versions it does
... besides the topic with the disabled AddIn.
I don't know if it's due to UpdateCheck.jsl , AddInLoad.jsl or if there is another reason.
It is not (always) the AddIn that has been updated which got disabled.
and it's not always the same AddIn which got kicked out.
Therefore, I wonder: In general, what triggers an AddIn to get disabled?