When a job is not found i.e. when visiting <sequenceserver-hostname>/this-job-definitelly-does-not-exist an exception is thrown. This results in exception notifications for those hosting sequenceserver instances. 404 not found is not an exceptional case, so perhaps it should be handled at the action level with a halt 404 and optionally rendering a dedicated 404 page.