when ironMQ returns a http 500 or really any thing fails before the worker specific code is called, could you consider adding a different state than "error" for those errors? I'de really like a separation of errors in my code and errors in the stuff that makes the worker run. I can infer it by seeing that the log is empty, but an explicit state for that would be really helpful
Right now I print out the payload first thing when my worker is called, if that's not in the log I know something failed outside of my control. It'd be nice to have a specific error type for this. I'de like all "error" states to be my fault.
carimura
commented
11 years ago
when ironMQ returns a http 500 or really any thing fails before the worker specific code is called, could you consider adding a different state than "error" for those errors? I'de really like a separation of errors in my code and errors in the stuff that makes the worker run. I can infer it by seeing that the log is empty, but an explicit state for that would be really helpful
Right now I print out the payload first thing when my worker is called, if that's not in the log I know something failed outside of my control. It'd be nice to have a specific error type for this. I'de like all "error" states to be my fault.