Query on Ratelimiting feature of DestinationService #1014

[pavan-singh-v-1290]

Ask the Question

Following up with this issue.
#1014 .

It was suggested to use getAllDestinationProperties() to get the list of all available destinations for the current tenant.
Then avoid calling destinations that are not in that list.

But destination what we are using is present for sure because same request is successful when we retry.

Regards,
Pavan

[rpanackal]

Hi @pavan-singh-v-1290 ,

Thanks for reaching out. We could use a bit more information from you to continue working on the issue.

Based on your description in the original issue #1014, there is the assumption that you are dealing with the bug mentioned in stack enterprise question.

Is the assumption true?

If it is true, then please wait for our next release (this week) as it includes a fix.
Otherwise, please follow our issue template to detail the problem you are facing, so we can understand/debug the issue.

[pavan-singh-v-1290]

Hi @rpanackal ,

Which release version will the fix be available?

[rpanackal]

Hello @pavan-singh-v-1290.

Unfortunately, the fix for the bug in detailed in stack enterprise question will take longer than anticipated. The fix is currently planned for the next release (5.26.0).

Thank you for your understanding.

[pavan-singh-v-1290]

Please let us know when the fix is available and can we have the question open till we have a fix.