Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
6 subscribers
Views
3852 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Hi I am calling a query rule through an expression rule in dashboard. I am
maheshbabuc
A Score Level 1
over 10 years ago
Hi
I am calling a query rule through an expression rule in dashboard. I am getting this error below.
Error:
Expression evaluation error in rule 'Queryrule' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query
Thank in advance...
OriginalPostID-121084
OriginalPostID-121084
Discussion posts and replies are publicly visible
0
colton.beck
Appian Employee
over 10 years ago
In my experience, this is usually related to the query rule timing out.
Check out the standard output logs for the day you received this error (e.g. jboss1-stdOut.log.2014-09-03).
Search through that for the query rule in question. The stacktrace should indicate the source of the error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
vineeta6579
over 10 years ago
it happens because of session timeout. logout and try again..
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Just like Colton mentioned this has to be investigated at the application-server.log level.
In order to troubleshoot issues where the message is very generic such as: "Unexpected error executing query" you need to reproduce and then find this error in the application-server.log, once you have identified it review each of the individual "Caused by" clauses. Usually the most bottom ones (that belong to that error) will be the most informative ones in the stack trace.
Query rules do not fail due to session time outs since they are evaluated at the server side.
We are talking about a possible time out of the query itself in the database engine, or an issue with the column mappings, etc but again, the best way to determine the root cause is looking at the "Caused by" clauses of the error in the application-server.log
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rohitr303
A Score Level 1
over 6 years ago
Any Suggestion as to how this issue was resolved ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel