Update 400 Automation Anywhere Wait Condutions

@tyronet2

Your bots are losing reliability and runtime to 400+ hard-coded delays that should instead respond to the actual readiness of SAP and banking UI elements. My background includes production automation, event-driven workflows, failure handling, testing, and Git-based delivery. At Marin Software, I built Python and AWS automation pipelines where each step depended on verified system state rather than arbitrary timing. I can apply that same discipline to each assigned batch: locate the fixed delay from the runbook, identify a stable object reference, replace it with the appropriate conditional wait, document the selector, and capture evidence from repeat runs before peer review. I’ll keep every change narrowly scoped so defects can be reviewed, reverted, and tracked independently without disrupting unrelated bot logic. Which Automation Anywhere version is deployed, and are the SAP and banking interfaces desktop clients, browser-based, or a mixture?

@FizzaNadeemK

Hi, I’m experienced with Automation Anywhere and SAP-style UI automation and can systematically replace hard-coded waits with reliable object-based waits. I’ll test each change through the required runs, document the object references, and submit clean batches of 5 defects for peer review. I’m available to start immediately and can take a high volume of defects while maintaining consistent quality.

@engruhulajom

Hello There! I'm Md Ruhul Ajom, and I'm excited to partner with you and I can dive into your project immediately. I have rich experience working with Automation Anywhere Object Cloning and dynamic wait conditions, converting fixed delays into element based waits for SAP and core banking processes. I understand you want 400 plus hard coded fixed wait actions replaced with dynamic object based waits targeting the correct SAP or banking UI elements, verified across two runs, commented inline for future reference, and validated with two consecutive days of error free execution, working in batches through your shared control room environment. I am skilled in Automation Anywhere, Object Cloning, and SAP UI navigation. I'm ready to start immediately and would be happy to discuss this project further or answer any questions you have. Looking forward to hearing from you. Best regards, Ruhul Ajom

@codeandcommand

Quoting per 5 defects makes sense, easier to track scope as you go. I have fixed wait conditions in Automation Anywhere bots before, usually a mix of dynamic wait clause tuning and replacing hardcoded delays. Can start today and knock out the first batch of 5 within 48 hours so you can check quality before committing further. The rate here is a starting point for one batch, we will lock in firmer numbers once I see the actual bot files. Want to send over the first 5 defects?

@Eliteinno

hello, This is a genuinely well-conceived improvement, since replacing hard-coded waits with dynamic object-based ones is exactly the right fix, so the real skill here is not just swapping the command but making each dynamic wait target the correct element reliably. The reason hard-coded waits exist is usually that the screen element is sometimes slow or inconsistent, so the craft is choosing an object reference that is genuinely stable, since an object wait pointed at an element that changes or loads unpredictably just trades a fixed delay for an intermittent failure, which in a banking or SAP process is worse than the slow wait it replaced. So on each conversion I would confirm the object clone targets a reliable, consistent anchor on that specific SAP or core-banking screen, since that is what makes the bot move the instant the element is ready without introducing new timeouts, which is precisely what your acceptance criteria are protecting with the two verified runs and the two-day stability check. That stability requirement is the right bar, since these processes are business-critical, so I would treat "passes peer review and runs clean for two days" as the real definition of done, not just the delay being removed. Working in your shared control room with only the default AA tools suits this well, and I would comment each change in-line with the object reference as you require, so future developers understand exactly what each dynamic wait targets. The batch-based flow, take items, convert, push for review, is a clean way to work through the 400-plus steadily and accurately. On your pricing structure, my per-five-defects quote is below, and I would want to confirm the object-cloning approach against one or two live screens first, since some SAP and banking elements clone cleanly while others need a more careful anchor, which affects the realistic pace. Are the target elements mostly standard SAP screens with stable object properties, or do some involve dynamic or custom UI where the object reference needs more care? And is the peer review done by your team, so my part is the conversion and the two-run verification before pushing? have a nice day.

@ahmaddar2970

Thanks for the detailed workflow and acceptance criteria. I can take this on in batches and convert the legacy fixed waits into dynamic, object-based waits using only Automation Anywhere default tools. I’ll work directly in your control-room environment, review the runbooks and task list, replace each hard-coded wait with the appropriate Object Cloning / Recorder / Wait for Window or Object step, and add clear inline comments for future maintenance. I’ll validate each change through the required two-run verification and focus on keeping the bots stable end-to-end across consecutive days. I’m comfortable moving quickly through SAP ByDesign and core-banking screens, so I can start with the first batch immediately and keep pushing reviewed updates as we go.

@Cruz1217

Hard‑coded waits become unreliable the moment SAP screen load times vary, which is why the current 400+ delays are a risk. I'll replace each static wait with a Wait for Object that watches the target element, using Automation Anywhere's Object Cloning to capture reliable selectors. Changes will be pushed through the shared control‑room workflow and reviewed before moving to the next batch. A common mistake is to copy a wait command without updating the object reference, which leaves the bot hanging on the wrong screen. You’ll see each updated step pass two clean runs, with comments in‑line, and the bot will keep processing without new timeouts.

@christopherm0620

Hi, Hard-coded wait x sec commands are the single biggest cause of bot flakiness and maintenance debt in Automation Anywhere estates driving SAP by Design and core-banking processes. If a screen layout or response time shifts, those waits either mask failures or force excessive idle time, increasing run costs and SLA misses. I have converted hundreds of fixed delays to object-based waits in Automation Anywhere using Object Cloning, Recorder, and Wait for Window/Object while working inside shared control-room environments. My recent work focused on SAP screens where I replaced brittle delays with waits that target stable attributes (id, title, tooltip, sibling text) and added in-line comments for peer review and auditability. I am comfortable navigating SAP by Design flows and core-banking sequences and will follow your runbooks and searchable task list. I will start by pulling the highest-failure items from your task list, open each bot in the control-room, remove the fixed delay, implement a Wait for Window/Object that targets the correct UI element (or fallback to existence/visibility checks), add concise inline comments describing the selector and intent, and execute the bot twice daily for two consecutive successful runs to meet acceptance criteria. - Would you prefer fixes quoted per 5 defects as a flat rate or a tiered rate based on selector complexity (simple element vs. composite XPath)? - Can you grant me read/write access to the control-room and the searchable task list so I can begin prioritizing and estimating the first batch? A quick call works for me whenever you are ready. Christopher

@Haya21dev

Hi there, I am an experienced Automation Anywhere (AA) Specialist with extensive experience in SAP and Core Banking UI automation. Replacing legacy hardcoded delays (Wait X sec) with dynamic Object Cloning / Universal Recorder "Wait for Object" logic is my bread and butter for making bots rock-solid and lightning-fast. My Approach to Your Bulk Fixes: Batch Processing: I will check out tasks in clean batches, replacing fixed delays with precise, object-based element detection (handling ready states, window focus, and object properties). SAP & Banking UI Experience: I am intimately familiar with SAP GUI/SAP ByDesign screen loading behaviors and dynamic UI elements. Inline Documentation & Git Workflow: Every fix will include standard inline commenting referencing the target object properties, committed strictly via your pull-request process. Rigorous Testing: Each fix will undergo dual-run validation to guarantee the 2-day zero-timeout acceptance criteria. Proposal & Quote: Fixed Rate: $30 per 5 fixed defects (fully tested & approved). Capacity: Ready to clear 15–25 defects per day starting immediately. I am ready to jump into your Control Room, grab my first batch, and start optimizing your estate today. Let's connect on chat to get started! Best regards, Muhammad

@Bhaveshb01

Hi, I’m interested in helping modernize your Automation Anywhere bots by replacing hard-coded fixed waits with reliable, dynamic object-based waits. My approach would be to review each identified wait, locate the correct UI/window/object condition, replace the static delay using Automation Anywhere’s native tools (Object Cloning, Recorder, Wait for Window/Object), and validate the workflow before submitting it for peer review. I’m comfortable working systematically through a large backlog and can start with a batch of 5 fixes as a pilot. I focus on making automation more reliable and efficient rather than simply replacing waits mechanically. I’d be happy to discuss your workflow and payment structure per 5 approved fixes. Best regards, Bhavesh

@BaileyG07

Hi there! Updating your Automation Anywhere estate sounds like a fantastic opportunity to enhance efficiency and reduce legacy issues. I understand the urgency of replacing hard-coded waits with dynamic object-based waits to ensure seamless bot performance. With extensive experience in Automation Anywhere and a strong grasp of SAP interfaces, I can efficiently navigate the shared control-room environment to implement the necessary changes. My approach will focus on thorough testing, ensuring each dynamic wait targets the correct screen element and meets your stringent acceptance criteria. You can expect timely execution with clear communication. I will work diligently to ensure each update passes peer review, minimizing any disruption to your ongoing processes. I can get started immediately and tackle multiple items from the pool daily. Let’s discuss how I can jump in and begin making these crucial updates. What’s the best way to kick off this collaboration?

@shammij2

Hi Replacing the hard-coded "wait x sec" commands with dynamic, object-based waits in your Automation Anywhere setup is crucial for optimizing and streamlining your SAP and core-banking processes. The key technical challenge here is to accurately implement waits that efficiently detect when an element is ready, utilizing Automation Anywhere's default tools like Object Cloning and Wait for Window/Object commands. My experience with AI-powered automation and process optimization aligns well with this task. I've successfully implemented dynamic waits in similar contexts, ensuring efficient bot operation without manual timeouts using Automation Anywhere before. I really appreciate the structured approach you've offered, with a comprehensive task list and a detailed workflow, which clearly indicates your commitment to precision and efficiency. I can help you swiftly update these waits and ensure seamless operation across your platforms. Let's dive deeper into the approach and get your processes running at top speed. Thanks, Shammi

@CliveMSoftware

I have hands-on experience with Automation Anywhere object cloning, wait conditions, and SAP UI navigation. I'll systematically work through your fixed wait pool, converting each hard-coded delay to a dynamic object wait targeting the exact screen element, then verify each fix runs clean for two consecutive days before submitting for peer review. I understand the per-5-defects pricing model and can batch process efficiently to maximize throughput. With access to your runbooks and task list, I can start on your first batch immediately and deliver multiple fixes daily. Let's get your legacy waits modernized and your bot reliability up.