Skip to main content
bhargavip7872
bhargavip7872
April 21, 2025
Question

Execute Procedure Smart Service error Query execution was interrupted (max_statement_time exceeded)

  • April 21, 2025
  • 10 replies
  • 0 views

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.

10 replies

stefanhelzle0001
stefanhelzle0001
April 21, 2025

I suggest to check for any table related issues, like locks.

bhargavip7872
bhargavip7872Author
April 21, 2025

Hi [mention:a11f77a729fb4db2af76b09948583328:e9ed411860ed4f2ba0265705b8793d05] 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

stefanhelzle0001
stefanhelzle0001
April 21, 2025

Any details in the tomcat stdout log file?

M
maguntajishnur2456
October 27, 2025

Hi [mention:484586e5bbd84be1a07ac4efa7e8b8a6:e9ed411860ed4f2ba0265705b8793d05] 

Were you able to identify the root cause of the error you encountered ? I'm currently facing a similar issue where a stored procedure that processes around 500 rows is failing in the higher environment, while the same code runs perfectly fine in both Dev and QA.

I'm wondering if optimizing the stored procedure is the only viable solution here, or if there might be other factors I'm overlooking. Any insights or suggestions would be greatly appreciated.

Thanks

Terms & ConditionsAccessibility statement