Thanks, that wasn't too bright of me!
I've changed it now.
I was surprised that I hadn't been inundated with error messages because of this, but the event hasn't fired for over an hour now.
However, the log is full of messages saying private messages were successfully received. The logging is done after the messages have been fetched, but before doing any processing:
I've assumed that the QueryAfterExecute event isn't thread specific, is that right?
Is there anything else that would stop the event from firing?
Cheers,
Josh
I've changed it now.
I was surprised that I hadn't been inundated with error messages because of this, but the event hasn't fired for over an hour now.
However, the log is full of messages saying private messages were successfully received. The logging is done after the messages have been fetched, but before doing any processing:
if (messages != null)
{
DefaultLog.Debug("Fetched Direct Messages (Outbound) for user {0}. Inserting or updating them in the database", user.DisplayName);
InboundPrivateMessage.Process(messages);
}
So something isn't quite right.I've assumed that the QueryAfterExecute event isn't thread specific, is that right?
Is there anything else that would stop the event from firing?
Cheers,
Josh