Let’s say an activity interceptor took a long time in the execute_activity method before forwarding the activity to the next interceptor. Would this time count against a heartbeat timeout?
On a similar note - would the schedule to start metric go to 0 as soon as the first interceptor starts? Or as soon as the last execute_activity in the chain (i.e. the activity itself) is called?
Would this time count against a heartbeat timeout?
yes it would
would the schedule to start metric go to 0 as soon as the first interceptor starts?
schedule to start from worker point of view is measured from when activity task is scheduled (on service side) until worker receives activity task and starts executing it. so yes, it not be after interceptor but before, as interceptor is considered part of activity execution