This is a feature request. Many external APIs have shallow rate limits. This means if you have an influx of calls to this API it's very likely you'll hit the limit and the call will fail. It would be great to be able to support defining a rate limiting strategy for a connector and provide the ability to retry after so long.
Context
Why is this change important to you? How would you use it?
It's something I've hit frequently while working with remote APIs, I'd use it for multiple integrations I've built.
How can it benefit other users?
Avoid hitting rate limits, losing data in failed calls
Detailed description
This is a feature request. Many external APIs have shallow rate limits. This means if you have an influx of calls to this API it's very likely you'll hit the limit and the call will fail. It would be great to be able to support defining a rate limiting strategy for a connector and provide the ability to retry after so long.
Context
Why is this change important to you? How would you use it?
How can it benefit other users?
Possible implementation
N/A