Temporal Actions

Community Support
1

Hi team, I am trying to understand the some of the cost associated with running in temporal cloud as described here. I had a few questions which I could not follow along from the documentation

  1. Workflow sleep: Do we consider a workflow.sleep as a timer action? And calling Workflow.sleep once result in a single action?
  2. Hearbeat actions: How do we account for heartbeat actions? Do activities send hearbeats when they are executing or even when idle? For a workflow with 10 actions is the following calculation correct?
    • Each activity sends a heartbeat every 8 seconds.
    • In one minute, there are 60/8 = 7.5 heartbeats.
    • In one hour, there are 7.5*60 = 450 heartbeats.
    • In one day (24 hours), there are 450*24 = 10,800
    • And for 10 activities a total of 108,000 heart beats
      - Or would temporal only send heartbeats when there is an active execution?
  3. Workflow Heartbeats: Do workflows send heartbeats to the server if so how do we account for them Especially if we have long running workflows which are mainly idle.

Would appreciate the help

2
  1. sleep uses a timer internally and is considered an action
  2. Heartbeats are sent every MIN(4/5* heartbeat timeout, 30 seconds) independently of how frequently they are called. They have to be called more frequently than the heartbeat timeout. Each activity heartbeat is counted as an action.
  3. Workflows don’t use heartbeats when idle.