Stuck on a recurring 409 Conflict error when updating intent entities via the Bot Builder API (/api/v2/bots/{botId}/languages/{languageCode}/intents). The integration handles bulk intent synchronization for a multi-org AppFoundry client, triggering updates every 300ms. While the initial creation succeeds, subsequent updates to the same intent ID fail with ConflictException: The resource was modified by another user or process. Debugging reveals that the ETag mismatch occurs despite using the If-Match header with the latest version from the prior GET request. The environment is us-east-1, and the client SDK version is 2.21.0. Rate limiting is not the issue, as the response headers indicate successful throttling compliance. The conflict seems to stem from asynchronous backend indexing processes modifying the intent metadata between the GET and PUT requests, invalidating the cached ETag. This behavior disrupts the idempotency guarantee expected for automated configuration management. Is there a recommended retry strategy with exponential backoff specifically for intent updates, or should the integration switch to a batch update endpoint to minimize race conditions? The current workaround of increasing the delay to 2 seconds degrades the user experience significantly.