YNAB will return a 429 status code if more than 200 requests per hour are made. This limit resets every hour on the hour. If a user's API key were to hit this limit it is likely that Refit will simply display an error message on the console. However, as I have never hit the limit in testing I am unsure how graceful this failure would be. It is possible the software would continue to try running, encountering further 429s. Need to investigate what happens when a 429 occurs and manage effectively. This can likely be configured across the entire application through refit configuration in ServiceCollectionExtensions.cs
YNAB will return a 429 status code if more than 200 requests per hour are made. This limit resets every hour on the hour. If a user's API key were to hit this limit it is likely that Refit will simply display an error message on the console. However, as I have never hit the limit in testing I am unsure how graceful this failure would be. It is possible the software would continue to try running, encountering further 429s. Need to investigate what happens when a 429 occurs and manage effectively. This can likely be configured across the entire application through refit configuration in ServiceCollectionExtensions.cs