Graceful handling of rate limits
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3489567. -->
Reported by: [yautja_cetanu](https://www.drupal.org/user/626050)
Related to !245
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Different ai provider accounts have different rate limits depending on the tier you are at. As testers we have got the highest tier as we use a lot of AI and want to try out later features but it means things we build sometimes doesn't work well with a newly created account with lower rate limits. </p>
<p>If you have a complex set of agents you send messages to the api as fast as possible. Which isn't THAT fast as you are regularly waiting for the ai to respond. </p>
<p>But still if you hit a rate limit there is nothing you can do about it right now apart from spend more money on a higher tier. </p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>- have better error messages informing the end user that they can likely upgrade their rate limit with their provider by paying for a higher tier. </p>
<p>- have a setting in advanced settings that can add a delay in milliseconds to send the prompts out slower. </p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<h3 id="summary-api-changes">API changes</h3>
<h3 id="summary-data-model-changes">Data model changes</h3>
issue