Hi Everyone,
I'm faced this error
Query execution was interrupted (max_statement_time exceeded)
two days in the model. Process model calls a SP which truncates the table an reset the autoincrement value of the primary key. This models runs twice in a day and this node failed in first run of the day for two days by throwing this error.
I'm aware why this error comes but nothing much to fix in the SP and also table didn't had much rows as well its around 800 rows. It might be DB usage might be high at that time but how i can confirm that from logs please let me know for suggestions.
Thanks,
Bhargavi P.
Discussion posts and replies are publicly visible
I suggest to check for any table related issues, like locks.
Hi Stefan Helzle No relations on the table, its a simple table we are writing task info no joins with any other tables. Its dump of task report from process. Also I didn't find that issue reported only two days
Any details in the tomcat stdout log file?
nothing much Stefan Helzle same error is coming. PFA
OK. This is not much to work with from my side ... not code, no details, no meaningful error messages ...
yeah not able to come to conclusion how it happened. Can we check if the DB usage was high or its under pressure at that time? which logs I can check
Is this the cloud DB?
https://docs.appian.com/suite/help/25.1/Cloud_Insights.html
https://docs.appian.com/suite/help/25.1/Appian_Cloud_FAQ.html#monitoring-&-alerting
yes its cloud, thanks for the inputs i wil have a look and is there any way to see of the table was locked at that time ?
Bhargavi Prakash said:is there any way to see of the table was locked at that time
I am sure there somehow is a way, but that would probably need support from Appian.