API errors are currently all set to STATUS_FAILED and cached. Some errors should ideally never be cached (e.g. 500 errors).
If it's not possible to differentiate between types of errors to support this, is there any reason why we can't just prevent caching of all failed calls?
API errors are currently all set to
STATUS_FAILED
and cached. Some errors should ideally never be cached (e.g. 500 errors).If it's not possible to differentiate between types of errors to support this, is there any reason why we can't just prevent caching of all failed calls?
Agileware ref GFCV-82