purrr
purrr copied to clipboard
can insistently capture root cause error? (feature request)
"insistently() and possibly() are a useful combination" - from purrr documentation
The combination of safely + insistently I would argue could also be very useful IF insistently captured the root cause error not just that "the function failed after retrying X times"
Then we can have a system that gives a function multiple chances to succeed but if this doesn't happen we can control the output via safely's otherwise parameter + we keep a record of why the function failed. I would see this as a complete and effective way to work with APIs and R/tidyverse. Thanks.