What version of DevTest you you have? Do you have the VSE Console/Portal open? My only guess is that it's coming from the VSE service status display on the web portal.
Are you seeing an actual problem with any VSE services, or is this just something that's filling up your log?
Have you used grep or your OS's equivalent to look for the same error in your entire log directory? Try just grepping/searching for 'queue-436AB017EB7E11E5A4A2F01FAF49ED85'. If it doesn't show up, then can you try turning the logging level up on your server?
Edit %DEVTEST_HOME%/logging.properties and find the following line:
log4j.rootCategory=INFO,A1
Change it to
log4j.rootCategory=DEBUG,A1
I'm pretty sure you don't have to restart everything; it takes effect automatically. Wait for the original log message to appear a few times in the VSE log, then revert the change. Don't leave this set at 'DEBUG' for very long, as it will produce a lot of logs. After you've done this, try to search for 'queue-436AB017EB7E11E5A4A2F01FAF49ED85' again.
Alternatively, you can search for the actual service(s) related to this error. You can take the 'queue-XXXX' part of the error and look in your project directory or directories for a file named 'Configs/project.assets/queue-XXXX.xml'.
There are actually four different 'asset not found' errors in your log. Three of them are getting logged once every five seconds like clockwork. Here are the corresponding file names to look for:
queue-30EBBB56EB5911E59B3BF01FAF49ED85.xml
queue-436AB017EB7E11E5A4A2F01FAF49ED85.xml
queue-7FC8BC49023611E6B1C3005056BD4E96.xml
And one is getting logged *twice* every five seconds. Maybe this queue appears in more than one VSE service?
queue-5F2E6424F4B211E5B1CF005056BD4E96.xml
If you find one of these files in a project then you should be able to open it with a text editor and visually find either the name of the asset (<Name>...</Name>), or the name of the queue (<Queue>...</Queue>). From there, you should be able to determine which VSE services use that queue asset.
If the VSE service is currently deployed then try re-deploying it to see if that particular error goes away. You could also just try restarting the entire VSE server to see if the error goes away.
If the service is not currently deployed, or if restarting the entire VSE server does not make the error go away, then maybe there is a bug where the web portal continues to query the status of VSE services that have been undeployed. That's my best guess right now as to what's going on without involving official support and hopping onto a Webex.