Unintended Activity Executions in Temporal Despite Not Being Called in Current Code

Developer Corner
1

Hello Temporal community,

I am encountering an issue where certain activities are being executed when I start my Temporal worker, even though these activities are not explicitly called anywhere in my current codebase. This behavior persists despite having made sure that I’m not referencing these activities in my workflow definitions. I don’t understand if this could be a cache issue or what?

Here’s what happens:

  • I start the Temporal worker, and the logs indicate that it’s running as expected.
  • However, activities that I previously used in the project (but have since removed from my current workflows) are still being executed.

Could anyone suggest what might be causing these activities to trigger and how to resolve this issue? Any advice on troubleshooting this further would be greatly appreciated.

Thank you in advance!

2

Check if you have any running executions where this activity was executed (before your changes to workflow code) where this activity is still retrying.

  • However, activities that I previously used in the project (but have since removed from my current workflows) are still being executed.

it sounds like you are still registering this activity with worker even tho its as you mention no longer being used?