# Automation Maintenance & Support | Flobotics Canonical: https://www.flobotics.io/maintenance-support --- [Home](https://www.flobotics.io/)/[What we do](https://www.flobotics.io/what-we-do)/Maintenance & Support Maintenance & Support # We maintain your automations. Even the ones we didn’t build. Automations need maintenance. Websites change, software gets updated, and processes change over time. We monitor your automations, investigate failures, make fixes, and keep them working. [Discuss your automations →](https://tidycal.com/team/flobotics/flobotics-intro-call-w) ## What we take care of ### Monitoring We check that each automation ran, how many cases it finished, and which ones it sent to your team. A run can end without errors and still miss work, so we look at the results, not only at the run. ### Fixing problems When an automation stops working, we find out what changed, fix it, and test it before it goes back into production. ### Updates & changes When an application, a website, a data format or a business rule changes, we update the automation to match. ### Improvements We improve existing automations so they handle more cases, make fewer errors or process work faster. ## Why automations stop working An automation works in systems that other people change. Most failures start with one of these. Sign-insA password expires, an account gets locked, or the multi-factor sign-in changes. Portals and websitesA payer changes its portal: a new page layout, a new field or a new rule for what it accepts. Software and outagesAn application, a browser or the machine the automation runs on gets updated, or a system is slow or down. DocumentsA form or a letter arrives in a layout the automation hasn’t seen before. DataA record is missing, doesn’t match another system, or is linked to the wrong account. RulesYour process, a payer’s rule or a coding convention changes. Some unfinished cases aren’t failures at all. The automation worked correctly and sent the case to your team because a person has to decide. When we look at a run, we tell the two apart. ## What happens when an automation breaks Example · payment posting · one weekMade-up data Run log - Mon 6:00128 payments128 posted - Tue 6:00135 payments134 posted · 1 to your team - Wed 6:00141 paymentsStopped after 37 postedRe-run after the fix · 102 posted · 2 to your team · 0 posted twice - Thu 6:00133 payments133 posted - Fri 6:00139 payments137 posted · 2 to your team What we did on Wednesday - NoticedThe run stopped after 37 of 141 payments. - Found the causeThe payer had shortened its portal sessions, so the portal signed the automation out in the middle of the run. - Fixed and testedThe automation now signs in again when a session ends. We tested the fix before the re-run. - Ran the restThe automation checked each payment before posting it. The 37 already posted were skipped, so nothing was posted twice. - ReportedWe told your team what happened and what we changed. Example with made-up data: payment posting from a payer portal. On Wednesday the portal signed the automation out in the middle of the run. We found the cause, fixed and tested it, posted the remaining payments without posting any twice, and told your team what changed.PauseReplay ## Someone else built your automations? We can take over. We maintain [UiPath](https://www.flobotics.io/uipath-services), Power Automate, Python and other custom automations, including ones built by your own team or another vendor. - ### Review what you have We look at your automations, the code, where they run, the accounts they use, the documentation and the problems you already know about. - ### Agree on what’s covered We agree on what to fix first, which automations we monitor, and what support includes. If an automation would be cheaper to rebuild than to fix, we tell you. - ### Start maintaining We take responsibility for those automations, look into every failure, and make the updates they need. If you have a [dedicated team](https://www.flobotics.io/dedicated-teams) with us, maintaining your automations is part of its work. If you only need support, we agree on which automations it covers and what it includes. [How we price →](https://www.flobotics.io/pricing) Client example ## We’ve taken over from other automation providers. One of the largest sugar producers in the world came to us after working with another RPA vendor. We started with SAP automations in controlling and finance, then moved into client service, sales and logistics. It became one of our longest partnerships. [Read the case study →](https://www.flobotics.io/case-studies/sugar-producer-automation) SAP automation program 4,685 h of manual work saved a year, across the whole automation program. Talk to us ## Need someone to maintain your automations? Show us what you run and what keeps going wrong. We’ll look at it and tell you what supporting it would involve. [Book a 30-minute call →](https://tidycal.com/team/flobotics/flobotics-intro-call-w)[Send us a message](https://www.flobotics.io/contact) 30-minute callKarl MielnickiCo-founder, CTO Show me what runs today and what keeps failing. I’ll tell you what we’d fix first and what taking it over would cost. Karl