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
2 replies
Subscribers
7 subscribers
Views
1102 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Environment: 7.9, No Hotfixes I'm running into some pretty strang
jamesm90
over 8 years ago
Environment: 7.9, No Hotfixes
I'm running into some pretty strange behavior that hopefully the community can help me with. A query entity is used to query a View, the entity selects only about half the columns in the view, filters on one column, sorts on another, and limits the batch size to 20. The rule errors out with: a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000). And we believe this to be a timeout error.
However, simply changing the batch size from 20 to -1 allows the queryEntity to run without error.
Why would the query time out when attempting to limit results to 20, but successfully runs (returning approx 700 rows) when not limiting the results? Is this addressed in a Hotfix? Is there some other platform setting to suspect? Could I avoid this error by switching to a query rule and passing a paging info with 20 batch size?
OriginalPostID-173242
OriginalPostID-173242
Discussion posts and replies are publicly visible
Parents
0
Tom Ryan
Appian Employee
over 8 years ago
Since this query completes successfully when you are returning the entire result set, it seems unlikely that this is timeout-related (unless you are sorting or filtering on large/complex/inefficient criteria).
To troubleshoot further you could try checking the database logs for any errors as well as increasing logging on both ends to try to get some further information.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Tom Ryan
Appian Employee
over 8 years ago
Since this query completes successfully when you are returning the entire result set, it seems unlikely that this is timeout-related (unless you are sorting or filtering on large/complex/inefficient criteria).
To troubleshoot further you could try checking the database logs for any errors as well as increasing logging on both ends to try to get some further information.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data