Activity associated with an agent changed, change not visible
We have 4 servers with one node each.
We have multiple agents.Pega Product Support
One Agent calls and activity that writes to log under a scenario.
I changed the activity to change the log message, however I don't see the change in log.
I logged to SMA and Started/Stopped the agent that calls the activity on each node.
Yet I don't see the change in log.
Not sure what I am missing. Please let me know.
***Updated by moderator: Lochan to add Categories***
Pegasystems Inc.
US
Hello Pushpa,
I assume you are talking about a custom agent. Does its access group define a major/minor/patch version for your ruleset that is lower than where you saved the new activity? Did you do a private checkout of the activity or forget to check it back in to the ruleset? What version of the product are you using?
Thanks,
Mike
HD Vest
US
Please see the attachments.
The main agent is in ruleset 01-01-96. The main agent does not seem be a rule.
the 1st agent in this main agent is the one I am referring....I changed my acitivity and saved it in 01.02.03.
Is that the problem?
When I go to main agent 01.01.96 and click on my agent activity...it takes to my activity that is in 01.02.03
HD Vest
US
In our UAT environment the change in the activity was picked but when I made a copy of the agent to a new version that matches with the activity.
That is both to be in ruleset version 01.02.03.
I did not have to stop/start agent. In UAT we have only one server.
I thought I found the solution, however yesterday I tried the same on production and the agent did not pick the activity.
I even stopped and started agents on all 4 production servers. Something is still missing even though the ruleset versions match.
Pegasystems Inc.
US
Hi Pushpa,
Can you try deleting all the "Agent-Schedule" instances corresponding to the specific agent from Dev portal > Records > SysAdmin > Agent Schedule screen, restart server/jvm and see if your agent gets triggered?
Pegasystems Inc.
US
Pushpa, Agent schedule instances are created by your system based out of your Agent rules and are tied to each PRPC node via the node id. These can be safely deleted, as the Master agent will re-generated these when it wakes up. I am suspecting its an environment issue as the same agent runs in another environment.