Actions
Bug #31844
openIf smart proxy remote execution returns 500, the job remains pending until some (1 hour?) timeout
Description
Since we know the smart proxy ended up with 500, we should fail the job and inform the user immediately with some guiding error message. This state is very confusing. The error message should tell user what log files to check if we can't print out the errror messge ourselves. For some reason, smart_proxy_dynflow_core printes errors in a warning level too, so users should be guided to enable some log level first.
No data to display
Actions