I need to call a stored procedure that takes a lot to complete (around 6min) and it does not return anything. It could be called in a async way that it would not matter.
Having said that, can I just use the timeout field to give it a short value (one second) being sure that in the DB, the SP will complete even if my Process model completes?Cheers
Discussion posts and replies are publicly visible
Since nobody else mentioned it yet: is the 6 minute run-time actually causing you any issues / errors? Do you have reason to believe it's actively preventing something necessary from happening?
I already see your feedback that it's already a short process and there are no parent processes depending on it, and that was going to be my only point of feedback too. Without that, I wouldn't worry about it unless it's actually failing on you sometimes.
Hi Mike,
Its not preventing anything, you are right. The only downside is that it sometimes shows as a possible improvement in the Health Check, as it says it is taking too long. That is the reason that I asked if I used the Timeout input Field with a short value, if it would have any downside.
joaor4842 said:I asked if I used the Timeout input Field with a short value
I think this would have effects you don't want, unfortunately. As in, if anything it will cause the procedure to abort before it's actually done. Though I haven't tested whether or not it actually would, or whether it would merely make the smart service proceed on while the procedure continues working in the back-end. You'd need to test this yourself, I believe - also consider that even if it "works" the way you want, it might cause an in-Appian error / warning to be thrown. Between the two options, honestly I'd take the health check warning (these are easy enough to flag as an extenuating circumstance, organizationally, and then ignore).