Hello all, I want to asked. I have one automation/flow that already published/deployed, when testing before published/deployed are successful but when already published/deployed this flow is not running. How to fix this problem?
Welcome to the community
Can you elaborate the issue…like some screenshots if any error…or if the trigger is not working?or anything else?
Cheers
Thank you @Anil_G
the trigger is not running/working whereas I already try running a trigger.
you mean when you send a new email the bot is not running?
did you happen to give any filters?
and is the connection active? and is the same connection configured in process as well or a different one?
cheers
yes when send a new email and result is not running,
I using filter based “CV” and “Curriculum Vitae” only.
all connections is active, one email address only, also same connection
looks like you dont have a license
you need robot units also as this is cloud robot
and in orchestrator=>tenant → machines , you need to create a cloud robot and add units to it
thats the reason it si not running
cheers
this flow using cloud serverless for runtime now, must using unattended robot for runtime?
Is there a relationship between event triggers and unattended robots?
btw you have tutorial how to create unattended robot?
As mentioned above you need to create a serverless machine and you need to have robot units to run
The steps are outlined above as well
If you are on community you might not have enough units
Cheers
thank you @Anil_G for your information.
I try this step and I will come back for share result of this. thank you again.
hello @Anil_G
I try using cloud serverless default because I have cloud serverless runtime but failed.
Atleast now you are able to trigger the process.as per error looks like the default serverless runs on .net8 and the is not compatible with .net8
cheers
Btw I already googling this error but they error using Studio Desktop (not Studio Web) then how to fix this error?
I already confused of this error haha
Update : I find one post : Automation faults because of package installation but not available best solution.
looks like an open issue.Package installation failed can be for many reasons and reason outlined here could not be fixed by us as we cannot login to the machine as well to know more
@loginerror - Any help here would be great
cheers
when I find other post that I update, the error same like me. I really very confused…
it means the machine can be accessed for everyone? sorry if I am newbie for this.
Cloud machines we cannot access…but for community to run robots a pool of machines would be dedicated
Cheers