What should I do when I hit a SeleID service limit?

Record the service, time, status and request identifier. Check reported usage and recent changes. Reduce duplicate requests and follow any documented retry delay. If usage appears below the limit, check the project and environment first, then include the request identifier when contacting support.

If usage appears below the limit, check the project and environment first, then include the request identifier when contacting support. Record the service, time, status and request identifier. If you need help, include the product you were using and the step that failed. Keep passwords, one-time codes and secret keys private.

Identify which SeleID service rejected the request and which limit it reported. Then check the service documentation for the relevant response, reset timing and any account controls. Pause avoidable retries while you diagnose the issue, and review your workload before assuming a higher allowance will fix it.