jscheffl commented on PR #46406: URL: https://github.com/apache/airflow/pull/46406#issuecomment-2669736539
> Extremely sorry for the delayed response, @jscheffl Lost track of this one when I got busy with another item. > > 422 is a status code we generally pass around if the request payload structure doesn't match what the API is expecting, ie. its an unprocessable entity. Example: https://stackoverflow.com/questions/59929028/python-fastapi-error-422-with-post-request-when-sending-json-data > > So I would question myself it 500 kind of fitted right in here. Does that make any sense? WDYT? Sorry, same here. Lost track of the open question in hundred of other emails and all other ongoing discussions :-D So I agree in general the 5xx error domain is the right thing _but_ it MUST be != 500 in my eyes as it is not a server but a content problem. Also there are many many other technical issues which can lead to a 500 - therefore I still am convinced that 500 should be retried - else any prod will be instable. I don't want to argue about every 500 that might be created because whatsoever small side effect in ops and check for failed tasks. So if we don't have any other 5xx error != 500 then (as above) the 4xx codes might be suitable. Especially for a broken XCom case that can not be de-serialized. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
