Why do RT activation list sometime shows multiple warm-started activations? | Community
Skip to main content
sarav_prakash
Community Advisor
Community Advisor
November 27, 2024
Solved

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

  • November 27, 2024
  • 2 replies
  • 711 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by sarav_prakash

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. 

2 replies

tmj
Adobe Employee
Adobe Employee
December 6, 2024

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
Community Advisor
sarav_prakashCommunity AdvisorAuthorAccepted solution
Community Advisor
December 20, 2024

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
Adobe Employee
Adobe Employee
December 22, 2024

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.