hello Siddhant, 

for listening also its found to weird for me, truly I don't the actually or correct answer because this is first time I am listening in the Outsystem

There are many way to do with this situation
(before that I just want to ask you one thing you are using timers or process ?) if no

- First delete the entity from your module and create new one that is the thing will also delete the data as well as the unwanted behavior for you (or do the cut past same entity to delete data may be this will also minimize your issue) for me I think this is the way to solved your error

- Second Add support ticket and ask Outsystem team for such scenario if possible connect to mail/phone 

hope this will solved your problem or you will get the appropriate answer as soon as possible

Keep coding :)

Thanks and Regards,

Akshay Deshpande

• This is reactive application, clear client side cache may be resolved if there is no recursive action wrote in internal flows. 
• Re publish the application and check. 
• Restart the environment

You can connect with Outsystems team, if not resolved issue. This is look like environment issue.

Regards,

Shahaji

Hi Akshay,

I have not included that entity in any timer nor it is being used in any logic. we are not able to delete the data, as after deleting the data we are not able to publish as getting execution timeout.

we have raised the issue with OutSystems as this app is on premises.

thank you all for the feedback

I tried the approach to increase the execution timeout to delete the data via SQL but didn’t success. However, with the help of Outsystems support we are able to fix the issue by recycle the worker process from the server which was running from last 30 hours for insertion. and it seems to be in some loop that got stuck and did not get override.

After that, I dropped the existing table and created the copy of it, it seems the loop that we inserted to create data was incorrect and result to infinite execution.