Symptoms:
When creating a job in SDL TMS using a Configuration supporting at least one non-wildcard Content Type and at least one wildcard Content Type that has no Excluded Extensions as well, tasks were created only for the files that matched the non-wildcard Content Types.

Explanation:
A chain of events was triggered at the database level and resulted in an incomplete list of available Content Types for job files to be associated with. The wildcard Content Types with no Excluded Extensions were missing.

Resolution:
Database level logic now allows for files to be associated with the available wildcard Content Types again.