ArgumentNullException at CheckDisconnectionsFixed

I get an error when reinstalling the plugin. Can you help ?

Failed to run a 60.00 timer in 'UltimateQueue v1.0.2' (ArgumentNullException: Value cannot be null.
Parameter name: source)
  at System.Linq.Enumerable.ToArray[TSource] (System.Collections.Generic.IEnumerable`1[T] source) [0x0000d] in <351e49e2a5bf4fd6beabb458ce2255f3>:0 
  at Oxide.Plugins.UltimateQueue.CheckDisconnections () [0x00015] in :0 
  at Oxide.Plugins.UltimateQueue.m__0 () [0x00000] in :0 
  at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in :0 

My configuration setting.

{
  "Auth Level required to skip queue no matter what (3 = none, 2 = admin, 1 = moderator)": 1,
  "Enable first connect skip queue?": false,
  "Enable Queue Capacity?": false,
  "If a player has one of the listed permissions, they are affected by queue capacity.": [
    "ultimatequeue.default"
  ],
  "Queue capacity": 50,
  "Enable Queue Holding?": false,
  "If a player has one of the listed permissions, their queue spot is held on disconnect": [
    "ultimatequeue.default",
    "ultimatequeue.vip"
  ],
  "Number of minutes to allow a user to reconnect without a queue": 2,
  "Enable Queue Skipping?": true,
  "If a player has one of the listed permissions, they will skip the queue": [
    "ultimatequeue.vip"
  ],
  "When a user joins for the first time, message the new user. Only works with first connect queue skip enabled": false,
  "When a user joins for the first time, announce it to all users. Only works with first connect queue skip enabled": false
}
Hi, I fixed this in the latest update. Please let me know if it's still an issue.

This is constantly writing. Is this a mistake?

[Ultimate Queue] CheckingDisconnections

[Better Chat] [Global] Garnizon: kabul ettim

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections

[Ultimate Queue] CheckingDisconnections
Hey yea this was a mistake - fixed in in v1.04
No problem right now. Thanks for your help.
Locked automatically