Evghenii Poliuhovici
Evghenii Poliuhovici
@jaredperreault-okta Thanks for answering. Dont have access to Internal Ref: [OKTA-645744](https://oktainc.atlassian.net/browse/OKTA-645744)
@jaredperreault-okta Thank you very much, I’ll wait, this change is important for us!
@jaredperreault-okta Yes, we use this `RequestExecutor` solution, but we still face the problem of exceeding the Api request limit. For this reason, I studied this article: https://developer.okta.com/docs/reference/rl-best-practices/ And I want...
@jaredperreault-okta Can you give an example using my code as an example? ``` import OktaSdk from '@okta/okta-sdk-nodejs'; const { Client, DefaultRequestExecutor } = OktaSdk; const customDefaultRequestExecutor = new DefaultRequestExecutor({ maxRetries:...
> @JekaPolihovic You can either extend the `DefaultRequestExecutor` class ([doc](https://github.com/okta/okta-sdk-nodejs/blob/master/README.md#building-a-custom-request-executor)) and override the `fetch` method, or you can subscribe to `customDefaultRequestExecutor.on('response', res => { ... } );`. > > However...
> @JekaPolihovic You can either extend the `DefaultRequestExecutor` class ([doc](https://github.com/okta/okta-sdk-nodejs/blob/master/README.md#building-a-custom-request-executor)) and override the `fetch` method, or you can subscribe to `customDefaultRequestExecutor.on('response', res => { ... } );`. > > However...
@jaredperreault-okta We want to ensure that error 429 does not occur even once, because if it does occur, this is already a problem for us. Even if it is processed...
> @JekaPolihovic Were you able to solve this issue using the `RequestExecutor`? I'm currently testing this! I will write how to solve this and we will close this issue.