I tried to create a process trigger scope activity and is working as expected from studio but when i try to publish the same I am getting below error.
To confirm the issue is caused by Trigger Scope I removed that activity and published and no issues then. The workflow doesn’t has many functions or activities
Thank you
Maybe the j needs to be in double quotes because it’s a string?
I tried with other triggers as well but I have the same issue. Its working when executed from Studio but not able to publish. This given trigger also is working from studio, issue is when I’m trying to publish.
I did try what you recommended, its the same
I would try different versions of UiPath.System.Activities. Could be a bug in the version you’re using.
Yes I did try downgrading to previous stable version of UiPath.System.Activities and UiAutomation activities. But it didn’t work.
I will try to use an older package version and recreate the flow again.
That didn’t work either
Hi @Athira
Would you mind attaching a zip of a dummy project that reproduces this issue, together with the information about the Studio version that you are using?
It would help us reproduce this issue.
Sure i will do that, i just don’t have access to machine right now. Anyhow the project doesn’t contain any other activity only the one shown in that screenshot. Also for this one i used the community version.
TestingPublishIssue.zip (2.6 KB)
Attaching the file
I am having the same problem…is there a fix for that?
No, It wasn’t part of any project. I was just trying to see how that function works. But didn’t work from community version that time.
would be nice to se a fix
using this example works
but if you copy the activity to a new project it doesnt work
Thanks for the project, it clearly continues to reproduce, even on the latest System and UIAutomation activity packages. We’ll have a look.
I can confirm that this will be fixed in the next Studio patch 23.10.1.
As a temporary workaround, and if your process supports it, one can use the local trigger standalone outside of the trigger scope (this is valid for local triggers only).
Thanks for looking into it!
I think I found a solution: take your main xaml (or the one which is the entrypoint) and call it by a new xaml with invoke Workflowfile and make this as your new entry point. Then no problem to publish.
Thanks for your effort, if it works someone could use this workaround until UiPath fixes the bug.
It definitely works! And it solves the Trigger Scope bug that for some reason still persists in UiPath 24.10.1. I don’t know if this is the same bug, or if a similar bug was just reintroduced, but nonetheless, this solution works here as well 
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.