I have a problem that I can’t understand. First let me explain my setup. I have a workflow running in a Spring container that executes several activities hosted in workers running in different other Spring containers. These activities might be called also by other workflows running in other containers (I hope this is not a problem). Also, consider that I am running all this on my Windows 10 laptop, so I’m running the temporal server as a docker compose (so I have a LOT of things running on my -small- box).
Anyway I just execute one workflow in this scenario.
The problem (I see this consistently, with different activities):
Here I call an activity named “SaveCustomer”, it takes 7+ minutes from schedule to start (but this can be because of my “crowded” setup), but what I can’t understand is why it takes 11 attempts (this number changes) to get the activity executed. The error I get:
But then the activity gets eventually executed.
Nevertheless, I’m sure the activity has been registered on temporal server and the worker started in the hosting Spring container.
Another thing I don’t understand is that I’ve set the options for the activity like this:
So the ScheduleToStartTimeout is set to expire after 1 minute, still the workflow (which has a longer expiration timeout) still attempts to execute the activity, regardless of its timeout.
Can someone please help clarify, and suggest if there is a way to mitigate these issues?