[ ] Introduce Loading component for Report while fetching from Airtable
[ ] In case of failure, use catch() to try again
NB. The latter seems to happen quite often on first try - could be that the AWS lambda instances take > 3ms to spin up and respond when first hit. So this should definitely be handled!
NB. The latter seems to happen quite often on first try - could be that the AWS lambda instances take > 3ms to spin up and respond when first hit. So this should definitely be handled!