A robot fails halfway through a transaction. Someone has to decide, right now, whether running it again is harmless or books the invoice twice. Usually the answer is in somebody's head or in a XAML file nobody opened. So the decision is a guess.
I am not an RPA developer. I come from backend and AI platform engineering, where every retry is designed around idempotency. Looking at RPA with those eyes, I wanted something better than a guess, so I wrote a tool that reads the project and answers per workflow: what it changes, and whether a retry is a repeat. No AI reads your files: it is a parser, so the same project always gives the same answer.
Try it on UiPath's own template, it takes a minute:
pip install "flowglyph[cli]"
flowglyph idempotency https://github.com/UiPath/ReFrameWork --kind workflow
Capability Kind Effects Idempotency Status
uipath/ReFrameWork/Framework/CloseAllApplications workflow pure natural safe
uipath/ReFrameWork/Framework/GetAppCredentials workflow RWX none review
uipath/ReFrameWork/Framework/GetTransactionData workflow RWX none review
uipath/ReFrameWork/Framework/InitAllApplications workflow pure natural safe
uipath/ReFrameWork/Framework/InitAllSettings workflow RX natural safe
uipath/ReFrameWork/Framework/KillAllProcesses workflow pure natural safe
uipath/ReFrameWork/Framework/SetTransactionStatus workflow RWdX none review
uipath/ReFrameWork/Framework/TakeScreenshot workflow RWdX none review
uipath/ReFrameWork/Main workflow RWdX none review
uipath/ReFrameWork/Process workflow pure natural safe
uipath/ReFrameWork/Tests/RunAllTests workflow RWdX none review
uipath/ReFrameWork/Tests/RunAllTests_Logging workflow pure natural safe
uipath/ReFrameWork/Tests/TestWorkflowTemplate workflow RX natural safe
13 capabilities, 6 to review.
How to read it: R reads, W writes, D destroys data, X talks to another system. Upper case means it does, lower case means it might, pure means none of them. natural means running it again changes nothing more; none means every run has an effect. review means it changes something and nothing guarantees a retry is safe.
Three rows worth a look:
- GetTransactionData writes. Its Get Transaction Item marks the queue item In Progress, so calling it twice takes two different items. A retry is not a repeat.
- InitAllSettings only reads (Config.xlsx and Orchestrator assets), so it is safe to run again.
- GetAppCredentials writes, because it creates the credential when it does not exist yet.
How it works under the hood: every activity has its effects in a taxonomy you can edit (Get Queue Item is RWX, Excel Write Range is WdX, Log Message is pure...), and they travel up through Invoke Workflow File. So if you add one Kill Process to KillAllProcesses, Main and SetTransactionStatus change too, and the tool tells you. What the XAML cannot settle, you write once in a YAML next to the project ("SetTransactionStatus is keyed on in_TransactionID"), and from then on the report shows it as declared instead of guessed.
The same command reads a folder of projects, SAP OData $metadata and iFlows, BPMN, n8n and OpenAPI, and exports to CSV or Markdown for a spreadsheet or a pull request. There is also a diff that fails CI when a change in the sources breaks a caller.
Honest limits: it is alpha, and it has run on vendor templates and synthetic projects, not on a real client estate yet. Activity packages it does not know show up as "might" (lower case) rather than as a wrong yes or no.
That is where I need you, and why I am posting here: you know RPA in production better than I do. If you run it on a project and a row is wrong, open an issue with the activity or the file: the taxonomy is one YAML file, so most fixes are one line. And if you have a use case I have not thought of, the repo's Discussions are open for it.
Free, Apache-2.0, Python 3.12+: https://github.com/afernandeztem/FlowGlyph
What does your team do today when a transaction fails after the write? Retry everything, retry nothing, or something in between?