I noticed that due to the contruction of the scheduled events class any errors that occur in it aren't linked to the particular line where the error qctually ocurred it merely says that it happend in the scheduled event. This makes debugging more complicated situations nightmarish. Fortunately there is the debug messaging and by putting in a few log messages one can sometimes work out the rough region in which the error occured by looking at which log messages never ran. This however is made more difficult by the rate limiting of messages - I'm aware in the docs it says that only identical messages will be rate limited but I am finding that when I try to debug a loop through a large number of pairs where for each message I append the unique pair name string I am still getting the rate limiting.  Is there anything that can be done about this as it makes the framework almost unusable for more complicated stratergies?