Skip to main content
Question

There was a problem at line 0 This may be due to the following reason: Fetch global values failed


Forum|alt.badge.img

Hi,

When I run any process, I get the error message “There was a problem at line 0 This may be due to the following reason: Fetch global values failed”, but it works fine after 2 or 3 retries.

2 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 570 replies
  • April 10, 2025

Any errors at line 0 indicate a problem with the pre-processing that happens on the Control Room side. Essentially, your bot gets compiled on the Control Room and sent to your Bot Agent for execution.

It sounds like there is a problem on the CR side with the global values. I would open a support ticket for further investigation.


jasthi bhaskar
Navigator | Tier 3
Forum|alt.badge.img+6

Hi ​@Sakshi, Check below steps 

 

1. Verify Network Stability

  • Ensure your machine has a stable internet connection.
  • Check for any network interruptions or firewall settings that might block communication with the A360 Control Room.
  • If you're on a VPN, ensure it's stable, as VPN disconnections can cause this issue.

2. Restart Bot Agent

  • Restart the Automation Anywhere Bot Agent service on your machine:
  • Go to Services (Windows: Window + R and write services.msc and Hit enter), find "Automation Anywhere Bot Agent," service in the console and restart it.
  • Alternatively, restart your machine to refresh the Bot Agent connection.

3. Check Control Room Status

  • Log into the A360 Control Room and ensure there are no ongoing server issues or maintenance activities.
  • If you're using an on-premise Control Room, check with your admin to confirm server health.

4. Validate Global Values

  • Go to the A360 Control Room > Manage > Global Values.
  • Check if the Global Values used by your bot are correctly configured:
  • Ensure the values exist and aren't locked by another user.
  • Verify that your bot has permission to access these values.

5. Update Bot Agent and A360

  • Ensure you're using the latest version of the Bot Agent and Control Room else update Bot agent version
  • Updates often include fixes for connectivity and synchronization issues.

6. Contact Support (If Needed)

  • If the issue persists, raise a ticket with Automation Anywhere support via the Customer portal
  • Provide logs from the Bot Agent (C:\ProgramData\AutomationAnywhere\Bot Agent\logs) and the Control Room audit logs to help diagnose the issue.

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings