How to handle the error "An extension of type 'UiPath.Activities.Contracts.Persistence.IPersistenceBookmarks' must be configured in order to run this workflow" when using Wait For Queue Item and Resume Activity?
Issue Description: How to handle the error "An extension of type 'UiPath.Activities.Contracts.Persistence.IPersistenceBookmarks' must be configured in order to run this workflow" when using Wait For Queue Item and Resume Activity?
Error Screenshot:
Root Cause: Respective package settings are Disabled.
Resolution:
Navigate to the Studio
In the "Project Panel"
Click on the "Activity Project Settings" as shown
Note: Activity Project Settings represent a set of changes that can be configured at the project level and applied to all activities part of project dependencies.
To configure activity properties at project level click the icon in the Project panel. The Project Settings window opens:
Enable "Support Persistence" toggle.
Before:
After:
By "Support Persistence" Definition: "Enable this option to mark that the process supports persistence and can save execution state on Orchestrator to accommodate human in the loop scenarios".
Click on "OK" in the populated window (Project Settings)
Run the workflow and no errors should be populated
If issue persists, follow the steps as shown discussed below.
Contact UiPath Product Support: If issue persists, create UiPath Support Ticket for further troubleshooting. Ensure to provide / attach the below list of details in ticket being created,
Error Screenshot
Robot Execution Logs
Upon reproducing the issue, please share us the event viewer logs: ETVX Logs
Is the issue happening on one machine or all the machines
In my opinion this should be added in the official DOCS because it’s a setting we MUST enable in order to be able to set up, for example, APPS actions projects.
This should be metioned somewhere in the DOC, as pre-config/pre-requisite
Thats designed and documented behaviour.
The persistence point HAS to be on the entry point workflow, typically the Main.xaml but depends on your project setup.
You cannot persist on an invoked workflow in any circumstance.
Its an underlying limitation of the Microsoft code (Windows Workflow Foundation) that UiPath is built on. To be honest its really cool we can set bookmarks (thats the underlying name for a persistence point) to pause a process and resume it, so I can accept this limitation.
It can for sure create some frustrations in design at first, but I have found with some time and careful design I can pretty much always work with it in a good way.
I’m curious why you guys are marking my response as generated by an LLM? Is this in response to be tagging some others and asking them to stop pasting LLM replies?
I dont think my reply reads like an LLM at all so curious why you’d tag it?
Ah, hahaha. That emoji is for tagging people who use an LLM to post a reply.
Coincidentally at the exact same time I got quite a few reactions on my post with that tag I was in conversation with someone asking them to stop posting LLM messages as replies to alot of topics as they weren’t helpful so it seemed like it could have been related.
Just funny coincidence
I think this marks my post count abit negatively now but thats no big deal
I can at least confirm that this isn’t used anywhere technically behind the scenes, and it’s purely decorative And we hope it’s obvious from the context that it is a user-driven thing and can sometimes be wrongly applied.