SyncFlow: top level heartbeat

[serprex]

was seeing heartbeat timeouts

[heavycrystal]

we lose more visibility into which phase of a batch we are in

[serprex]

yes, tho with parallelism heartbeats were already stepping over each other. With changes to parallelism in last normalize change I'm wanting to move towards parallelism being on by default

[iskakaushik]

@serprex - can we have this heartbeat contain a message that shows the consolidated status of syncs and normalizes, something like:

{
   start_sync_batch_id: ...,
   start_normalize_batch_id: ...,
   current_sync_batch_id: ...,
   current_sync_batch_start_time_utc: ...,
   current_normalize_batch_id: ...,
   current_normalize_start_time_utc: ...,
   current_time_utc: ...
}

[serprex]

updated with heartbeat state I think will be useful. Temporal already has timestamps on heartbeat, no need to put timestamps in message

[heavycrystal]

nit: could probably store some of these in substruct of FlowableActivity and keep calls clean