Why do RT activation list sometime shows multiple warm-started activations?

[sarav_prakash]

I am running a job on AppBuilder project. I created an action; set the web='no'; created trigger and rule, so every 5 mins action invokes successfully. 

I deployed the same action into 2 workspaces. I observe that one of workspace alone runs multiple activations, while other workspace runs correctly with single activation. Here is an example activation list.

Here there is cold start for every 5 mins. After cold start, always there are 3 warm starts. Any given instance, 3 activation pods are running. 

Impact is, same event is getting processed 3 times and sometimes resulting in errors. Is there a way to trash duplicate activations and keep it clean?

[tmj]

Hi @sarav_prakash, in the workspace where there are more than expected activations, do you have another trigger that is invoking the action?

[sarav_prakash · Accepted solution]

I raised adobe ticket and found out, this specific workspace pod alone seemed to be corrupted. I created a new workspace and not facing this issue. 

One symptom for this issue was, during development I was creating multiple trigger rules as oneminutetrigger, twominutetrigger, fiveminutetrigger. These multiple triggers somehow stuck to package. Even when I did clean deploy by undeploying previous package completely, multiple triggers were hanging unable to list or kill. 

Deleting workspace and creating new workspace only solve my issue. 

[tmj]

Yes, we need to show you all the triggers in the app and allow you to delete the older ones. It's not currently available, so your best bet is to deploy to a fresh workspace.