Evaluating SQL TRACE Logs

Hi,

I am evaluating SQL TRACE logs to understand how Appian at the back end runs the select query.

While evaluating, I am frequently able to see the following query multiple times, infact in milli secs:

select this_.id as id26_2_, this_.started_ts as started2_26_2_, this_.status as status26_2_, 
this_.test_data_id as test4_26_2_, this_.test_job_id as test5_26_2_, testjob2_.id as id12_0_, 
testjob2_.created_by as created3_12_0_, testjob2_.created_ts as created2_12_0_, user3_.id as id1_1_, 
user3_.scs_key_h as scs2_1_1_, user3_.scs_key_salt as scs3_1_1_, user3_.username as username1_1_ 
from test_queue this_ inner join test_job testjob2_ on this_.test_job_id=testjob2_.id left outer join usr user3_ on testjob2_.created_by=user3_.id 
where this_.status=? order by this_.started_ts asc limit ?

However, there is no table/view with name "test_queue" that any of my application is hitting, rather the table/view is non existent in my database.

So I would like to know, why Appian is actually evaluating this query. Is it some cache that Appian is maintaining with this query so something else.