Indeed, there was $contents, not $filename - but the issue went way deeper: Errors detected during parsing of the JSON request were not properly propagated as error message - and for another reason, failure of load_capture_request() did /NOT/ trigger the task to go to error.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed, there was $contents, not $filename - but the issue went way deeper: Errors detected during parsing of the JSON request were not properly propagated as error message - and for another reason, failure of load_capture_request() did /NOT/ trigger the task to go to error.
Fixed in rev.563:
Error messages and handling in general has been improved (using RuntimeExceptions).