We have a process model that inserts records into a table and then we call a stored procedure that will execute and perform an update action on the newly inserted records while running it the process model is executing successfully and records are getting inserted but it seems the execute stored procedure node is not executing. also, the node is not giving any errors, yet it is taking some time to process but the update is not done. Can anyone help on what might be the probable reason? Is it going out of scope?
Screenshot of the PM where the node has been added:
Discussion posts and replies are publicly visible
Hi ShaliniD Did you check all the parameters in execute smart service node? Did you provide all the required inputs that trigger the process model node
We need more details. How do you know that the SP was executed?
DO you have transactions in yout sp? Or conditional statements? Maybe the Sp is rolling back the transaction or the flow is going through a path that makes nothing?
When we are trying to execute separately it is executed so it is correct
We have checked the instances and it does not show any errors
yes
ShaliniD said:yet it is taking some time to process but the update is not done.
What are you trying to say?? Correct me if i'm wrong Process completing without errors(Store procedure Node execution, is it happening?) ,But Values are not getting updated??
Yes, the node is executing but values are not updated. Yet when we are creating a separate PM and just executing the Stored Procedure everything is happening properly the way it should execute
Execute Store procedure requires External sync . Why is there Write records After Execute Store procedure? Are you trying to save back updated values and writing them using Write records(Output from store procedure is Anytype ,No cating errors?)?? is there a particular reason behind it? Can't you directly use Sync records??
You can check the log files to see if there was some error. If not, you should inset the data from the process and then run the SP on the database directly to understand if it is the SP or the Process Model that is causing this issue.
With this, you should have some clarity on what you need to debug.