Output Module Error Response, raising awareness.

Recently I got an error on my custom java flows that my outputmodules gerenerate an error 500.

If not mistaken is an error 500 on the product/server side.

Apparently it was me that made a mistake a few months ago that wrote “vocabulary” instead of “Vocabulary”.
(this has worked for months)

Can we please raise some awareness on the ErrorHandeling and Error logging, especially for something as crucial as the outputmodule?
In the hope they improve this.
Cause a mistake as this should not cause an error 500.

I’ve wasted a full day on this on fixing this.

jonasvan_reeth

Posted 5 years ago · Edited 1 year ago·Last reply 5 years ago

2 comments

Former User

·5 years ago · Edited

This is pretty annoying… I had a piece of code left in Proof of Concept because I couldn’t figure out why the outputModule was spitting out an error code 500 every once in a while and working other times. … turns out the issue was more or less what you explained.

With the improvements to workflow logging, I’m hoping similar changes are made across the board.

I imagine the error handling would have been a bit more intuitive if you were hitting the outputModule via the Java APIs - which makes this even more annoying lol

bartvanderlocht

·5 years ago · Edited

Plus 1 for better error handling in the outputModule (also wasted too much time in the past to fix mistakes in my json’s)