autobotAI
Bot Library
Pricing
Documentation
Resources
Partner Central

Troubleshooting Guide for Executing Bots in autobotAI

This guide helps you identify and resolve common issues that might occur while executing bots in autobotAI. Follow the steps below to troubleshoot effectively:

Common Issues and Solutions

1. Bot Execution Fails

Possible Causes:

  1. Insufficient permissions.
  2. Incorrect configuration settings.

Troubleshooting Steps:

  • Verify that the bot has the necessary permissions to access required resources. Check them in the permissions required to execute the bot in the bot details section.
  • Ensure that any external integrations (e.g., cloud platforms, APIs) are correctly set up and active.
  • Review the execution details for detailed error messages and fix the highlighted issues.

2. Integration Issues

Possible Causes:

  1. Misconfigured integrations.
  2. API rate limits or access restrictions.
  3. Inactive integrations.

Troubleshooting Steps:

  • Confirm that the integration credentials (e.g., API keys) are accurate and active.
  • Check the integration’s status in the autobotAI integrations.
  • Verify that API limits are not exceeded.
  • Test the integration if necessary.

3. Execution Delays

Possible Causes:

  1. Network latency.
  2. High resource usage on the execution environment.

Troubleshooting Steps:

  • Test your network connection to ensure stability.
  • Monitor the resource usage of the environment where the bot is running.
  • Scale up resources if needed.
  • Optimize the bot’s workflow for better performance.

4. Unexpected Bot Termination

Possible Causes:

  1. Unhandled exceptions.
  2. Runtime errors.

Troubleshooting Steps:

  • Review the error logs for details on the termination.
  • Add error handling mechanisms in the bot’s workflow.
  • Test the bot for edge cases to prevent similar issues.
  • Update the bot to handle unexpected scenarios.

5. Bot Output is Incorrect

Possible Causes:

  1. Logic errors in the bot's workflow.
  2. Outdated data or parameters.

Troubleshooting Steps:

  • Double-check the bots workflow to ensure the logic is correctly defined.
  • Validate the input data and parameters being used.
  • Update any dependencies or libraries if applicable.
  • Test the bot with sample data to isolate the issue.

6. Insight Schedule Configuration Issues

Possible Causes:

  1. Misconfigured schedule settings.
  2. Incorrect time zone settings.

Troubleshooting Steps:

  • Verify that the schedule is correctly configured in the Insight section.
  • Ensure the correct time zone is selected for scheduling.
  • Test the schedule by setting up a small test job to confirm functionality.

7. AI Assistant Not Working

Possible Causes:

  1. Misconfigured AI models.
  2. Connectivity issues.
  3. Subscription or billing issues affecting AI assistant availability.

Troubleshooting Steps:

  • Check that AI models are properly configured in the user settings.
  • Verify that there are no connectivity issues between the AI assistant and the autobotAI platform.
  • Ensure that the subscription plan is active and that the account is not facing any billing issues.

8. AI Generated Node with "+" Not Working Accurately

Possible Causes:

  1. Issue with the AI model.
  2. Incorrect or unclear prompt.

Troubleshooting Steps:

  • Review the AI model settings to ensure that it's functioning as expected.
  • Revisit the prompt to check if it requires refinement or better context.

9. Approval Node Notification Not Coming

Possible Causes:

  1. Misconfigured notification settings (e.g., incorrect recipients or inactive communication methods).
  2. Approval node not properly triggered.

Troubleshooting Steps:

  • Verify that notification settings for the approval node are configured correctly.
  • Ensure that email recipients are valid and the communication method is enabled.
  • Check that the approval node has been correctly triggered.

10. Notification and Approval Node Format Issues

Possible Causes:

  1. Incorrect use of handlebars for dynamic values.
  2. Formatting issues in the notification template.

Troubleshooting Steps:

  • Ensure the correct syntax is used when referencing variables in the node's format.
  • Double-check the use of handlebars in the notification template.
  • Test the template with sample data to verify the output format.

11. AI Params Not Using Previous Node $$ Variable Value (Large Data Arrays)

Possible Causes:

  1. Large context size causing truncation.
  2. Incorrect reference to previous node's $$ variable.

Troubleshooting Steps:

  • Ensure that the previous node's variable is being passed correctly to the AI params.
  • Optimize the data array to reduce size or split it into smaller chunks.
  • Verify that the variable reference is correctly formatted and used within the AI params.

12. Unable to Iterate Through All Values of Previous Node (Large Data Sets)

Possible Causes:

  1. Insufficient memory or processing capacity.
  2. Looping logic issues.

Troubleshooting Steps:

  • Optimize the iteration logic to handle larger data sets efficiently.
  • Consider paginating or batching the data if possible.
  • Scale up resources if needed to handle large data sets.

13. Unable to Add Previous Node Value to AI Evaluator (Large Context Size)

Possible Causes:

  1. Context size limitations.
  2. Incorrect variable reference.

Troubleshooting Steps:

  • Review the context size limitations in the AI evaluator.
  • Split large context data into smaller, manageable pieces.
  • Ensure that the previous node's value is correctly referenced.

14. Linux Agent and Kubernetes Agent Not Reporting to autobotAI API Node

Possible Causes:

  1. Connectivity issues.
  2. Agent misconfiguration.

Troubleshooting Steps:

  • Verify that the Linux/Kubernetes agents are correctly configured and have proper access to the autobotAI API.
  • Check the network connection and firewall settings.
  • Restart the agent service and verify if the issue persists.

15. AWS SES Integration Not Sending Emails

Possible Causes:

  1. Misconfigured SES settings.

Troubleshooting Steps:

  • Check the SES configuration in autobotAI and verify the SMTP settings.
  • Test the SES configuration using a simple email.

16. Kubernetes Agent Related Troubleshooting

Possible Causes:

  1. Misconfigured Kubernetes settings.
  2. Network connectivity issues.

Troubleshooting Steps:

  • Verify the Kubernetes cluster settings and ensure the agent is correctly registered.
  • Check for network or firewall issues blocking communication with the autobotAI API.
  • Restart the Kubernetes agent and verify logs for any errors.

17. Terraform Not Executing in Linux Integration

Possible Causes:

  1. Incorrect Terraform configuration.
  2. Permission issues.

Troubleshooting Steps:

  • Verify that Terraform is installed and configured correctly on the Linux system.
  • Check for any permission-related issues preventing execution.
  • Run Terraform commands manually on the Linux machine to identify the root cause.

18. Ansible Execution Issues in Linux Integration

Possible Causes:

  1. Misconfigured Ansible playbooks.
  2. Missing dependencies.

Troubleshooting Steps:

  • Review the Ansible playbooks and ensure they are correctly configured.
  • Verify that all necessary dependencies and roles are installed on the Linux system.
  • Test the playbook execution manually to check for errors.

Additional Tips

  1. Always keep your bots and integrations updated to the latest version.
  2. Regularly monitor bot performance and execution details logs.
  3. Reach out to autobotAI support for unresolved issues or advanced troubleshooting assistance.

Need Further Assistance?

If you are unable to resolve the issue, please contact autobotAI support or refer to the documentation for additional guidance.

Back
using ai management
Next
bot