Instances with default term collections associated it might happen that terms were not checked automatically after import.
Description
problem
On some instances the terminology was not checked anymore.
Mostly when TermCollections were set automatically.
reason
The info in the task that it contains terminology was calculated to late. So the autoqa worker doing term check might be initialised with wrong terminology flag value in DB.