If you look at the audit_log and audit_log_changes table, you see that the entries listed don't seem to line up with what the client shows. Checking the audit_log_crawl table shows that the last entry crawled was ID 365824096744767488, which corresponds to 2017-10-06 11:34:21.347000 UTC which seems a bit out of date.
The audit log and channel history crawlers are both using the same logic, so something weird is happening here.
Some ideas:
something's wrong with the audit log part of the crawling
audit log history fetching has some sort of fundamental difference in how it behaves
the scheduling of the coroutines is preventing the audit log crawler from ever doing any work
If you look at the
audit_logandaudit_log_changestable, you see that the entries listed don't seem to line up with what the client shows. Checking theaudit_log_crawltable shows that the last entry crawled was ID365824096744767488, which corresponds to2017-10-06 11:34:21.347000 UTCwhich seems a bit out of date.The audit log and channel history crawlers are both using the same logic, so something weird is happening here.
Some ideas: