You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to process a new intent value, the NlpService encounters an error during the synchronization phase. While the log sometimes indicates successful syncing (New value successfully synced!), it repeatedly throws errors stating Unable to sync a new value.
The root cause appears to be a subsequent operation within the sync process, specifically an attempt to update an existing NlpValue record. The detailed error message Error: Unable to update NlpValue with criteria "67fe3ba7bf07ef4e4d07d9d8" indicates that the NlpValueRepository.updateOne method fails when trying to find and modify the record matching that specific criteria string (likely an ID).
This failure occurs within the NlpService.handleValueCreate function, which is likely triggered by an event after the initial creation attempt. The problem lies not necessarily in the initial insertion but in the follow-up update/synchronization step for this particular record.
The text was updated successfully, but these errors were encountered:
When attempting to process a new intent value, the NlpService encounters an error during the synchronization phase. While the log sometimes indicates successful syncing (New value successfully synced!), it repeatedly throws errors stating Unable to sync a new value.
The root cause appears to be a subsequent operation within the sync process, specifically an attempt to update an existing NlpValue record. The detailed error message Error: Unable to update NlpValue with criteria "67fe3ba7bf07ef4e4d07d9d8" indicates that the NlpValueRepository.updateOne method fails when trying to find and modify the record matching that specific criteria string (likely an ID).
This failure occurs within the NlpService.handleValueCreate function, which is likely triggered by an event after the initial creation attempt. The problem lies not necessarily in the initial insertion but in the follow-up update/synchronization step for this particular record.
The text was updated successfully, but these errors were encountered: