🗝️ Some automation issues require development support. ADO tickets help engineers review logs, diagnose errors and resolve platform-level issues.
⚠️ Important: Only raise ADO tickets after confirming the issue is not caused by user error or configuration problems.
When to Raise an ADO Ticket
Repeated automation failures with no visible error explanation.
Errors appearing across multiple automations for the same user.
Inconsistent data in Leads Lists or Activity logs.
Suspected LinkedIn session or login issues not resolved by schedule adjustments.
Prepare Required Information
Collect the Automation ID.
Gather screenshots of errors or unusual activity.
Note the date/time the automation last ran.
Confirm whether the user was logged into LinkedIn at the time.
Provide the LinkedIn URL used in the automation.
Submit the ADO Ticket
Open the RPA Automation Ticket Template in ADO.
Complete all required fields, including automation ID and description.
Submit for triage — routing automatically assigns the ticket to the appropriate developer.
After Submitting
Monitor ticket updates for developer feedback or requests.
Inform the user if additional data is required.
Confirm resolution and advise the user when the automation can resume.
💡 Best Practices
Always remove sensitive candidate data from screenshots before attaching.
Provide specific timestamps to help developers identify failures in logs.
Avoid raising duplicate tickets for the same issue.
🤔 FAQs
Q1: Who should have ADO access?
Answer: Only internal team members; customers do not access ADO.
Q2: Should failed actions be replayed before raising a ticket?
Answer: No, failed steps should not be manually re-executed. Escalate instead.