Runner doubt

If your bot suddenly stops working, follow these steps:
2. Check Logs: Review the logs for any errors or warning messages that might indicate the cause.
3. Bot Status: Verify the machine status of the bot in the Robility Manager to ensure it is not faulted.
4. System Health: Check the health of the system in Runner or the server where the bot is running.
5. Dependencies: Ensure all dependencies and external systems the bot relies on are operational.
6. Contact Support: If you are unable to resolve the issue, contact Robility support for further assistance.

Posted by: @abidurai

↑

If your bot suddenly stops working, follow these steps:
2. Check Logs: Review the logs for any errors or warning messages that might indicate the cause.
3. Bot Status: Verify the machine status of the bot in the Robility Manager to ensure it is not faulted.
4. System Health: Check the health of the system in Runner or the server where the bot is running.
5. Dependencies: Ensure all dependencies and external systems the bot relies on are operational.
6. Contact Support: If you are unable to resolve the issue, contact Robility support for further assistance.

What do I need to do when the log reports “Permission denied” when adding transactions to the Interact?

@iffhiba When the log reports “Permission denied” while adding transactions to the Interact, follow these steps:
1. Check API Permissions: Ensure the “API” permissions are provided.
2. Login to Robility Manager: Navigate to your project.
3. Go to Interact Workflow Menu: Access the project configuration menu and check the “Queue” steps.
4. Verify Queue Access: For each queue, select “Queue Access” and check if “API” access for the respective machines has been provided.
5. Adjust Permissions: If the permissions are not correctly set, adjust them accordingly to provide the required access.
User reply: Thanks for your quick response, now the bot is running successfully without any issues.