e2core Errors in user-written Runnables shouldn't control Atmo's HTTP response status code

Errors in user-written Runnables shouldn't control Atmo's HTTP response status code

Open danielledeleo opened this issue 3 years ago • 1 comments

Currently, if a Runnable returns an error that status code gets passed all the way through to Atmo.

Atmo's HTTP response codes should reflect the state of Atmo, not the state of the Runnable.

Nov 18 '21 18:11 danielledeleo

This ONLY applies in headless mode, in normal mode the Runnable should be able to determine the status code

Nov 19 '21 17:11 cohix