Como andan? Actualmente mi stack es blue prism y power automate(desktop y cloud) con casi 4 años de experiencia, y prácticamente no existen ofertas para ninguna de las herramientas.
Con el avance de la ia deberia cambiar el enfoque de mi perfil? Siento que esto esta mas que condenado y quiero mejorar mi empleabilidad pero no se a que herramienta o disciplina disparar. Qa sería una opción?
Oi pessoal. Vejo que muita coisa no meu trabalho daria para automatizar então como sempre tive vontade de aprender e num ambiente de negócio que me agrada, quero agregar isso a minha função. Porém estou sem saber o que aprender, onde, qual a sequência e etc. Cheguei até me matricular num curso da PUC-MG, mas sai bem antes de terminar porque era muito ruim, muito ruim mesmo e não queria jogar mais dinheiro fora. Alguém poderia me instruir para essa jornada?
building something that fills portals with no api and I'm stuck on the boring part. submit gets clicked, confirmation never loads. do you look the record up before retrying, or have you found something better?
I'm an automation analyst. My job is mostly the BA side: I meet with process owners, map the as-is process, and decide whether and how it should be automated before it goes to a developer. Our stack is RPA (Fortra Automate) plus Power Platform, with custom scripts as a last resort.
I'd like my handoff docs to actually help the devs, not just pass a review. If you've ever been handed a Process Definition Document (PDD), or the start of a Solution Design Document (SDD), and had to start building from it:
What info do you always end up chasing down that should have been in there from the start?
Which sections do you skip or never use?
How do you want exceptions and edge cases written up? A table, a flowchart, screenshots, something else?
What details about systems, access, or credentials help you get started faster?
Where do you think the PDD should end and the SDD begin?
Bonus points for examples of a really good or really bad handoff. Thanks!
I’m currently building an RPA bot using Power Automate Desktop to automate a pharmacy prescription and dispensing workflow on a legacy desktop system, and I'm running into a major design bottleneck regarding performance, exception handling, and logging.
I’m testing two different approaches (JSON vs. XML inputs), and both have distinct trade-offs that I'm struggling to balance:
1. The JSON Approach (Item-by-Item)
How it works: We loop through the JSON data using a For Each loop and enter each medicine into the application one by one.
The Good: Exception logging is straightforward. If a specific drug fails due to stock issues, warnings, or missing barcodes, we know exactly which drug failed and can easily write the exact drug name, barcode, and error reason into an Excel exception report for the pharmacist.
The Bad: It is very slow because we are checking pop-ups, handling UI elements, and processing validations for every single drug individually—exacerbated by the sluggishness of the legacy system.
2. The XML Approach (Pre-filled / Bulk)
How it works: We paste/load the XML data, which pre-fills the form and patient details, and use a standard loop/clicks to process the script view.
The Good: Much faster execution because data is pre-populated in bulk.
The Bad / The Issue: Because everything is handled in a bulk/pre-filled view rather than an itemized For Each drug loop, when a warning pop-up or validation error occurs on the legacy app, I cannot easily track which specific drug caused the failure. As a result, I don't know what drug name to put into the Excel exception sheet for the pharmacist to review.
Performance & Error Handling Roadblocks in this Legacy Environment:
Using multiple If window contains checks and On block error subflows to catch various pop-ups makes the overall execution quite slow and introduces visible delays (especially since legacy UI elements take time to load).
When using standard loops instead of itemized loops, mapping an unexpected error back to the exact array item/drug name becomes extremely difficult.
My Questions to the Community:
How do you usually handle exception logging when working with pre-filled forms or XML-based bulk data in PAD where items aren't processed via a strict For Each loop?
What are the best practices for handling dynamic pop-up detection on a slow legacy application without heavily lagging the bot with continuous If window contains or On Block Error actions?
Any advice, structural patterns, or best practices would be greatly appreciated!
Hi everyone, I'm looking for a full-time role in RPA or full-stack development, working with Python, Vue, and Django. I'm the developer of LiberRPA, which I recently shared here.
I started teaching myself RPA in September 2020 and began using it in my work. I've worked mainly at consulting firms, delivering automation projects using UiPath, Encoo and UiBot. I have a solid understanding of RPA architecture and core concepts, so I can quickly learn and work with whichever RPA platform a project requires. Much of my growth has also come from learning on my own. I enjoy learning new skills and turning what I learn into working software.
I also enjoy thinking about how to make projects easier to develop and maintain. That's what led me to build LiberRPA, an open-source RPA toolchain. My recent 0.4.0 post shows some of those ideas in practice.
When I decided to build LiberRPA, I left my full-time job. I wanted to develop it independently and avoid possible disputes over ownership of the project. For about two years, I've worked on it without a steady job, with my partner's support.
With 0.4.0 released, I'm ready to return to full-time work. I also want to earn a steady income and share more of the financial responsibility at home.
I'm currently based in mainland China and willing to relocate. I would need a work permit for a role abroad.
The code and documentation are public, so you can see how I approach software design and development. If you think my experience could help your team, please send me a message on Reddit or email me at [email protected]. I'd be happy to talk about the role and how I could contribute.
Ciao a tutti, Sto usando Playwright per automatizzare un processo di inserimento dati su Salesforce (Lightning). Non si tratta di test: è un'automazione in stile RPA e l'accesso tramite API non è un'opzione, quindi tutto deve passare attraverso l'interfaccia utente.
Vorrei strutturarlo con un Page Object Model (o simile), ma scrivere e gestire manualmente i Page Object per Salesforce è complicato: ID dinamici, Shadow DOM nei Lightning Web Components, caricamenti di pagina lenti e incoerenti.
Quello che mi piacerebbe sapere:
Generazione di POM: esistono strumenti o script che generano Page Object (locator e azioni) dalle pagine di Salesforce? Qualcosa di meglio di CodeGen per questo scopo?
Approcci assistiti dall'IA: Qualcuno ha mai utilizzato LLM o agenti (Playwright MCP, Copilot, Claude, Cursor…) per generare o gestire oggetti pagina per Salesforce? Quanto sono stati affidabili?
Strategia di localizzazione: Cosa funziona meglio su Lightning? Localizzatori basati su ruoli/etichette, attributi data-* o altro?
Robustezza: Come gestite tempi di attesa, spinner, toast e aggiornamenti di release di Salesforce che potrebbero compromettere i vostri selettori?
Alternative: Utilizzereste Playwright per questo scopo o optereste per uno strumento RPA?
Stack: TypeScript + Playwright, in esecuzione automatica.
Qualsiasi strumento, repository o esperienza appresa sarebbe molto apprezzata.
When I shared LiberRPA 0.3.0 here, a central Console was still on the roadmap. With 0.4.0, it is now available, including a free public service.
For anyone new to the project, LiberRPA is an open-source RPA toolchain for Windows. A flowchart shows the main process, while ordinary Python files contain the detailed logic. You work with both in VS Code.
Visualize the process. Code the logic.
I'm an RPA developer with several years of experience. I enjoy writing code, and I spend a lot of time thinking about how to make projects easier to develop and maintain. Those priorities are why I started LiberRPA.
With Console, I put that same care into the everyday work around running an automation. Here are a few details I'd like to show:
Preparing and starting another run. From a past run, you can open a new run request for the same project using its most recently uploaded package. You can review and edit the settings before starting it. You can also select shared, non-secret Assets as project inputs, so common values can be managed in Console.
Checking what actually happened. Run details show the inputs used and the outputs captured when the flow ends. Logs have highlighting, text filtering, and automatic refresh, so you can follow a running project or inspect its recorded messages afterward.
Sending useful run emails. You can configure emails for start, completion, and error events, with your own subject and message. You can insert input values into the text, and completion or error emails can include output values too. This lets the notification carry information about the actual task.
Console also includes package version management, Executors and Executor Groups, schedules, retries, data queues, shared files, and department access controls. An audit log records actions within the organization. You may already be familiar with these features from commercial RPA platforms. I hope having them in LiberRPA gives you another reason to try it.
There is an HTTP API for starting work, checking results, and accessing shared resources. This allows an existing business system to call an automation and use its results as part of a larger process.
Projects still run on your Windows Executors. Console manages the work and collects the results.
The tools and Console are open source, and the public Console is free to use.
There are no paid tiers. I've aimed to provide enough capacity for frequent use, with limits to protect the shared service from abuse. If you prefer your own server or need a private network, you can host Console yourself.
You can also continue to develop and run projects locally without Console.
LiberRPA is still in alpha. If you give it a try, a small project is a good place to start.
I'd like to hear which of these details would help in your own work, and what you would still find inconvenient. If another tool handles something better, please tell me about the task and the difference. Your suggestion might make it into a future release.
I'm building LiberRPA for the long term. Your feedback will help me decide what to improve next, and I'm happy to help if you get stuck.
for people running uipath / power automate etc on browser stuff, what breaks most? selectors changing, mfa, popups, new tabs, timing? and how do you usually find out it broke? before or after someone notice
Hi guys, I just started learning RPA, hope I am not late to the show. What are the career tips that you can share with someone that is starting RPA from a UX design background?
Anyone interested in automation, agents, and orchestration check out this UiPath Orlando Community Day event happening November 19! There will be industry experts from UiPath showcasing how agentic systems and coding agents are transforming automation. Check the link to RSVP!
Hola a todos. Vengo a pedir consejo y a abrir perspectivas
Quede como unico responsable tecnico de un entorno RPA (Blue Prism) que configuró y a dado soporte un externo, ahora mismo no esta disponible el soporte. Tengo relativamente poca experiencia en la herramienta y estoy aprendiendo sobre la marcha. Para colmo, NO existe ambiente de desarrollo ni de pruebas: todo lo que toco entra directo a produccion. Y varios de los objetos son compartidos por muchos procesos, asi que un cambio en el lugar equivocado puede romper varias automatizaciones a la vez.
Como trabajo hoy para no romper nada? cuando necesito corregir o mejorar algo, clono el objeto y el proceso a copias aisladas ("harness"), creo una cola de prueba aparte, meto interruptores (kill-switches) con variables de entorno y un "modo sin envio real" para no gatillar acciones reales, pruebo ahi y recien despues replico el cambio a mano en produccion. Funciona y me da tranquilidad, pero es lento, muy manual y siento que no es la forma "correcta" de hacerlo.
Lo que me gustaria que me orienten:
Como trabajan ustedes cuando NO hay ambiente de pruebas? Vale la pena montar un entorno de desarrollo independiente (instancia/BD local) aunque sea solo para mi? Que tan factible es?
Hay una forma mejor que clonar a mano? Me suena usar export/import de paquetes entre entornos, pero no se si es la practica recomendada ni los riesgos. Como manejan el versionado y los respaldos de los artefactos?
El tema de los objetos compartidos me tiene nervioso. Como reducen el "radio de impacto" de un cambio? Separan por grupos/permisos, duplican, refactorizan?
Siendo el unico responsable y sin soporte del proveedor, que me recomendarian priorizar para profesionalizar esto y bajar el riesgo? Cualquier recurso, guia, curso o buena practica es bienvenido.
Y una mas de fondo: este escenario (unico responsable, sin soporte, sin ambiente de pruebas) es tan rojo como lo siento, o es mas comun de lo que creo? Que argumentos usaron ustedes para conseguir presupuesto/entorno/soporte?
Agradezco cualquier experiencia o consejo, incluso si es "lo estas haciendo mal, parte por aca". La idea es abrir frentes nuevos para encarar esto mejor. Gracias!
Hi everyone, I’m a UiPath Developer with 7 years of experience. I started my career directly with UiPath, so I never got the chance to learn web development, frontend, backend, or even strong programming fundamentals. To be honest, I genuinely loved RPA. When I was new to IT, I used to spend weekends building automation projects, trying interesting use cases from YouTube, learning new features, and solving automation challenges just for fun. I was really passionate about it. This was around 6 years ago. Now, after 7 years, I’m in a very different situation. I’ve only worked on UiPath throughout my career and haven’t had the opportunity to work with other technologies. I’m currently working at an MNC with a salary of around ₹19 LPA. With AI evolving so quickly, I feel the RPA market isn’t as strong as it used to be. Development has become much faster, and many tasks that once required experienced developers can now be completed by junior developers with the help of AI. That makes me wonder what my long-term career looks like. Since I don’t have a strong programming background, I’m finding it difficult to transition into another domain. At times, it feels like I’ve become too specialized in one tool. So I wanted to ask: Has anyone else with a similar background faced this situation? What are you doing to stay relevant? Should I continue investing in the UiPath + AI ecosystem, or is it better to start learning software development from scratch? If you were in my position today, what would your roadmap look like? I’d really appreciate honest advice from people who have been through something similar or have successfully transitioned into another role. Thanks in advance!
In today’s data-driven enterprises, browser automation through Robotic Process Automation (RPA) tools- such as Selenium, Robot Framework, or custom scripts- is widely used to automate repetitive tasks like logging into dashboards, extracting data, and syncing it into internal systems. These automations are often fragile: a minor UI change- say, a login flow shifting from password to OTP- can silently break scripts. Traditional bots simply fail with generic errors like “element not found,” causing disruptions in data pipelines and business operations.
What’s missing is a dynamic, intelligent layer on top of existing RPA tools- one that not only detects breaking changes but also understands the context and heals or adapts in real-time without human intervention.
Desired Solution:
Participants are expected to develop an adaptive automation framework that enhances existing RPA solutions using the power of Large Language Models (LLMs). The system should act as a smart wrapper around current scripts and offer:
Real-Time Change Detection: Monitor automation runs and intelligently flag or diagnose failures caused by DOM, structure, or flow changes- beyond basic error messages.
Context-Aware Adaptation: Use LLMs to analyze the updated DOM or flow and suggest (or apply) fixes to selectors, navigation logic, or data extraction routines.
Self-Healing Capability: Where possible, auto-correct minor issues (like updated element IDs or positions) and retry execution without breaking the workflow.
Plugin-Friendly Architecture: Should wrap seamlessly around tools like Selenium, Playwright, or Robot Framework- without requiring complete rewriting of existing test suites.
Traceability & Logging: Offer smart logs and human-readable explanations for failures and attempted fixes, improving visibility and debugging.
Anyone who has maintained RPA bots knows the two classic pains: a selector breaks as soon as the site changes, and every automation needs a developer to build and maintain it, far from the person who actually knows the task.
I've been building ANCHOR, a research project at my university in Brazil, to try a different split. The person who knows the task describes it in plain language ("Register Maria Silva, IT department, contractor, and save"), and the system runs it in the browser. It runs locally, with small open models through Ollama (Qwen 3.5, 4B and 9B) on a 4 GB GPU, so no data leaves the machine.
Who controls what
The LLM only plans. It turns the request into steps, using the names of the elements on the page. It never clicks anything.
A deterministic heuristic finds each element, and refuses when it isn't sure.
Then the user decides: the candidates are numbered on the page, the user picks one, and the choice is remembered for the next runs.
What matters for day-to-day RPA (version 0.3)
Saved automations: the task is learned once with the model, then replayed without it, in about 3 s per run, with parameters and one run per row of a spreadsheet.
When the site changes, a saved automation recovers (by asking the user, or by replanning with the model when no one is there), keeps the fix, and records it: what failed, what replaced it, and how. Every recovery can be reviewed and undone.
Sensitive actions ask first: deleting, saving, sending, paying, downloading, uploading, cancelling something irreversible. The decision is saved per automation.
Each action's effect is checked (the page changed, the field kept the value, no error appeared), and the end of a run is checked against what was actually done, so a run that didn't do the task doesn't end as a success.
Page content can't give orders: instructions hidden in pages are treated as data.
A benchmark against a classic script
30 tasks on pages altered in 5 levels (renamed IDs and classes, synonyms like "Save" becoming "Submit", restructured layouts, cookie banners and hidden sections, lookalike decoys and injected instructions), 150 runs per executor and model, with no user:
Executor
Tasks done
False successes
Fixed-selector script
53%
0
LLM in control (4B / 9B)
68% / 72%
33 / 41
ANCHOR (4B / 9B)
82% / 84%
2 / 1
The script was perfect where labels changed (it doesn't read them) and failed where IDs and structure changed; the LLM in control often claimed success without doing the task. ANCHOR's weak spot is content hidden behind a "Show more" button. These are development numbers; a closed test set is waiting for the 1.0 run.
What's next: uploads, downloads, new tabs and data extraction (0.4), then a local interface with a "Run" button per saved automation (0.5).
I'd really value feedback from people who build and maintain bots: would you trust a bot that recovers on its own if every fix is recorded and undoable? What would you need to see before using something like this on a real process? And if you try it, failure cases on real sites are the most useful thing you can send me.
Disclosure: this is my own project. I designed the system and the evaluation, and wrote the code with help from an AI assistant (Claude). English isn't my first language, so I also used it to help write this post.
I’m currently working on my Bachelor’s thesis about AI-based process automation and human–AI collaboration in the workplace.
As part of my research, I’m conducting a short survey focusing on people who have experience working with AI-based automation, RPA, Intelligent Process Automation, Intelligent Document Processing, or similar automation technologies.
The survey explores topics such as:
how automation affects manual workload and creates new tasks,
how employees experience errors and exception handling,
trust in AI-based automation,
and how automation influences human decision-making and autonomy at work.
⏱️ It takes approximately 5–7 minutes to complete.
If you have experience working with these technologies, I would really appreciate your participation. Your responses will be used solely for academic research as part of my Bachelor’s thesis.
Hi everyone! I’ve been working in RPA for several years and I’m now seriously thinking about transitioning from traditional RPA into AI/AI Engineering or AI-related roles. I’d love to hear from people who have actually made this transition. If you started as an RPA Developer/Engineer and moved into AI, could you share: What AI role did you transition into? (AI Engineer, ML Engineer, GenAI Engineer, AI Automation, AI Solutions Architect, etc.) How many years of RPA experience did you have before making the move? What did you learn first, and what was your learning roadmap? Which courses, certifications, books, YouTube channels, or other resources actually helped?
It would be incredibly helpful for those of us in RPA who want to move toward AI without throwing away the experience we’ve already built. Thanks in advance! 🙏
I've spent 8+ years in enterprise RPA and honestly? The drag-and-drop approach drives me crazy. It kills developer creativity, locks you into vendor ecosystems, and costs a fortune.
So out of pure spite, I built something different.
BotMonitor lets you write your automations in plain Python no proprietary studio, no drag-and-drop, no vendor lock-in. You register your scripts, and the platform handles the monitoring: live status, execution history, error logs, all in one dashboard. You don't share your code or your data. Just the signals it needs.
I couldn't find any serious RPA tool built around Python, so I made one. Two years of nights and weekends while managing a full-time job.
Community edition is free. Would love honest feedback from this community botmonitor.in