Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Error handling by storing error and tool details which causes error in DB.

AnchalJain
5 - Atom

Hi All,

I am new to Alteryx and looking for error handling options, apart from event (on error).
I need to store the tool name (which causes error) and error details in SQL database in case my workflow get failed.

In Snaplogic, we have error pipeline. If any snap causes error in main pipeline, we can call error pipeline and store the error, snap name, pipeline name and time in database.
Do we have any option like this in Alteryx.

Appreciate quick help on this.

Thanks 
Anchal

6 REPLIES 6
BrandonB
Alteryx
Alteryx

If this workflow is running on the Alteryx Server, the run logs will contain the tools and errors. You would be interested in the Engine Logs: https://help.alteryx.com/20201/server/log-files 

AnchalJain
5 - Atom

Hi,

 

Thanks for your response.
I can get the error and tool name from log files, but I need to capture it in SQL database.
I need to add it as code in my workflow, so that if workflow fails it capture the error in database at the same time.

BrandonB
Alteryx
Alteryx

Error logs can only be written to a logging directory, so if you want to have it subsequently write to a SQL database you will need to use some code as well to extend that functionality. You can see an example of how that has been done here: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Workflow-Error-Log-Output/td-p/558489 

AnchalJain
5 - Atom

Hi,

 

Thanks a lot for the link shared. It will help.

AkshataK
5 - Atom

Hi Brandon, The link seems to be archived now. Would you have another example where this requirement has been achieved? 

BrandonB
Alteryx
Alteryx

@AkshataK since then Alteryx has released customer managed telemetry which provides quite a bit more information than previous methods: https://community.alteryx.com/t5/Engine-Works/Customer-Managed-Telemetry-A-Window-into-Workflow-Tran... 

 

This article shows how to enable it. 

 

If you would like to use the older methods you can follow the answer in this link: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Save-workflow-log-in-SQL-database/td-p/1...

 

"You can either enable a setting in the Alteryx System Settings under Engine > General and add a path in the Logging Directory field. Anytime the server runs a workflow, the message log will be written to that location and named with the timestamp (EPOCH formatted) for when the job started.

 

The other option would be pulling it directly from Alteryx Servers MongoDB, which can be a bit tedious if you're not familiar with the collection schema."

Labels