No, there is no way to extend the timeout for the SQLcommand being run.. It appears to be using the default of 30 seconds.. The queries involved here are not overly complex, so I'm a bit surprised that you would be getting timeouts.. I "believe" based on what I'm seeing in the screen capture, that the following query is being run at the time of the timeout;
SELECT (COUNT(DISTINCT Name)) FROM _RES_COLL_<LicensedIncludecollection> Where ArchitectureKey = 5 AND IsActive = 1
Where "<LicensedIncludecollection>" is the collectionID of the collection that you have specified for the Licensed collection setting found under settings->website.
The only other query we are running in this area of the code is as follows:
SELECT (COUNT(DISTINCT Name)) FROM v_FullCollectionMembership Where ResourceType = 5 AND IsActive = 1
‎Sep 30, 2020 02:39 PM
‎Sep 30, 2020 02:46 PM
‎Sep 30, 2020 03:43 PM
It's random and its not everyday. If it isnt concerning then we won't worry about it. We are trying to clean up the error log as much as possible.
‎Sep 30, 2020 03:45 PM