Has anyone run into this error before? We have a rule that calls a stored procedure given an input, then returns results. One day a user ran into an issue where the SP was returning null, but the next day the SP was returning results. We've done no code changes, so I took a look into the logs and found this error:
Where it says Error Msg = ORA-01013: user requested cancel of current operation. However, I know the user ran into this on the UI only and didn't cancel anything on the backend. It also seems like it was not a timeout issue since upon checking rdbms logs, the execution times were very low.
Does anyone have any suggestions on what this might be or what we should look at for further investigation?
Discussion posts and replies are publicly visible
Appian sends a query or procedure call to Oracle through a JDBC connection. If Oracle does not respond within the configured timeout, Appian tells the JDBC driver to cancel the operation.
This generates a request to abort the current execution on the Oracle side.
If the operation is not immediately cancelled (due to locks, system load, etc.), Oracle may continue processing it for a short time.
This can result in an ORA-01013: user requested cancel of current operation error in Oracle and a timeout or aborted call error in Appian.
This is in theory, because according to your message the execution time is low.......... Did you check Oracle logs?