You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user wants a callback when the API call errors. We had this functionality, but it was removed at the design phase.
A simple way of emulating the same feature is having an error-handling post-processing step. Normally, when the API response is non-2XX, the Airnode always calls back fail(). We can have an errorHandlingPostProcessing snippet that only gets invoked when the API returns a non-2XX code and post-processes the API response to call back fulfill() with that.
The text was updated successfully, but these errors were encountered:
This was a user on discord. I would say low priority because the user themselves admitted / recognized "my use-case is very niche" and there are creative workarounds that @bbenligiraymentioned, like a proxy or FailedRequest watcher, that could suffice if the feature is badly needed.
I think we should have this or something analogous at some point, but it shouldn't be included in our foreseeable plans. So I created the issue to document it for the future.
The user wants a callback when the API call errors. We had this functionality, but it was removed at the design phase.
A simple way of emulating the same feature is having an error-handling post-processing step. Normally, when the API response is non-2XX, the Airnode always calls back
fail()
. We can have anerrorHandlingPostProcessing
snippet that only gets invoked when the API returns a non-2XX code and post-processes the API response to call backfulfill()
with that.The text was updated successfully, but these errors were encountered: