I have an entity based record that when I open in Tempo is giving an error spora

In the rules interface, if create a test query rule to query this database, do you get any results back?

yes I get the results in the rules interface.
In the tempo it is sporadic. If I get the error once, If I click back again few times it opens fine.

I've seen this issue when there problems with the SAIL expression itself. Can we minimize your SAIL expression to narrow down whether it is the rule or if it is related to rendering your Tempo Record?

I will try your suggestion and will narrow it down but the fact is since it is sporadic it's hard to troubleshoot. I also noticed two things.
1) The record tags in news events will show "not available" sometimes.
2) the record dashboard will NOT always display latest changes in the database. It could take up to a minute for the changes to show up.

These might all be related issues somehow

Both behaviors you were seeing could be related to your database.
1) Can you confirm that you have complete connectivity to your database?
2) There may be a slight delay with your database, or that your query is not optimized and it's causing a little delay to return the results.

1) The SQL id configured with the data source has reader and writer access to the database
2) This error sometime happens when we open the record type at which point there wouldn't be any query rules but just list view template correct?

BTW, not sure if it matters but we are on Appian 7.3, WebSphere and SQL Server

Are you using an image in your ListViewItem expression? If so, try switching the order of the ListViewItem attributes so that the image is declared before any expressions.

Actually the image is the first one.. below is my list view item

='type!{www.appian.com/.../2009}ListViewItem'(
image: if(rf!Type="F",cons!ICON_F_TYPE,if(rf!Type="P",cons!ICON_P_TYPE,cons!ICON_T_TYPE)),
title: proper(rf!IName),
details: "Target Date: "&rf!TargetDate&chr(13)&"RNum: "&rf!RNum
)

For testing purposes, what happens if you DON'T use an expressions to define your image. After a bit of testing, do you notice that the error gets thrown? If not, add the expression back in, and see if the behavior changes.