I have an app published to our Gallery that fails after about 3.5 to 4 hours of processing with the message "There was an unknown error executing the application. The engine reported status Error". To troubleshoot: * I have pulled the job results from the Gallery API but there is no detailed messaging. * I checked our Server configuration and the job timeout is set to 0. Has anyone else encountered this? What was the solution?

@morr-co I am really happy that this has been solved for you somehow.

I was finally able to produce some of the errors running the files asynchronously and it was in fact related to memory. We converted the job to run the files in smaller batches and were able to have the whole thing complete successfully.

@morr-co I think this issue is specific to the Alteryx Server and Mongo DB itself. Reading these links: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Dynamic-Input-tool-causes-quot-Document-0-is-too-large-for-the/m-p/618804 https://community.alteryx.com/t5/Alteryx-Server-Discussions/Document-0-is-too-large-for-the-cluster-generic-mongodb-18/m-p/612161 they may give you some ideas. Are you able to run the workflow in Designer that is installed on the Server Machine?

There was an unknown error executing the application. The engine reported status Error

morr-co

I have an app published to our Gallery that fails after about 3.5 to 4 hours of processing with the message "There was an unknown error executing the application. The engine reported status Error". To troubleshoot:

I have pulled the job results from the Gallery API but there is no detailed messaging.
I checked our Server configuration and the job timeout is set to 0.

Has anyone else encountered this? What was the solution?

Gallery

Error Message

Server

Accepted answers

All comments

rkapoor

@morr-co I would advise having a look at the workflow log on the Server. Do you have access to this?

What is your workflow / app doing? - Are you accessing databases or accessing other networks?

morr-co

Hi @rkapoor - my suspicion is that the machine is running out of memory as the error always occurs after about 3.5 or 4 hours. We are currently modifying the workflows to run the files individually rather than all at once. There were no details when I pulled the job status from the Gallery API but I think you are referring to the logs in the MongoDB?

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703