Donnerstag, 21. April 2016

Inexistent session parameter makes workflow fail

I just had a workflow fail because a session parameter was not given any value on run time. I figured out that this parameter was used in the error logging part of the session.
I switched off logging to DB and also in the default session config.
However, the error persisted.


I exported the workflow from the Repository Manager and checked the resulting XML for the string of the violating parameter but it was not there!


Solution: I finally changed, in the session, the DB connection to an existing DB connection and switched DB logging off after that.


Remark: Maybe the re-Import of the XML would do the trick too.

Keine Kommentare:

Kommentar veröffentlichen