Common Issues and Troubleshooting
3.16.4 Common Issues and Troubleshooting
- Issue: Unable to Access Version Log Module
- Description: Users experience difficulties accessing the Version Log module via the navigation path.
- Resolution:
- Action: Verify user permissions and ensure that the user has the necessary access rights.
- Steps:
- Check if the user has the appropriate role (e.g., Admin, Team Lead) that grants access to the Version Log module.
- Confirm that there are no system outages or connectivity issues affecting module access.
- Retry accessing the module after verifying permissions.
- Contact support if access issues persist.
- Issue: Version Timeline Not Displaying Correctly
- Description: The timeline view does not show all bot versions or displays incorrect statuses.
- Resolution:
- Action: Ensure that the bot versions have been properly trained and published.
- Steps:
- Verify that the training and publishing processes were completed without errors.
- Check for any synchronization issues between the bot training system and the Version Log module.
- Refresh the module or clear browser cache to resolve display issues.
- Contact support if discrepancies continue.
- Issue: Failed Status Without Reason
- Description: A bot version is marked as Failed, but no reason is provided.
- Resolution:
- Action: Investigate system logs or contact support to identify the cause of the failure.
- Steps:
- Check the Failed Reason field for any hidden or detailed logs.
- Review system logs for any error messages related to bot training.
- Retry the training process and monitor for any issues.
- Contact support if the reason remains unidentified.
- Issue: Incorrect Status Display
- Description: A bot version shows an incorrect status (e.g., Active instead of In Progress).
- Resolution:
- Action: Refresh the module and verify the current state of the bot version.
- Steps:
- Refresh the Version Log module to update the status display.
- Confirm the actual state of the bot version through the training system.
- If discrepancies persist, clear browser cache or try accessing the module from a different browser.
- Contact support if the issue remains unresolved.
Next