Fix the approved source revision
Synthetic absence LV2 revisionR2 replaces R1 and is already approved. Team calendar acknowledges R2; reception calendar acknowledges R1 only. Local administration closes propagation only when both acknowledge R2. It does not reconsider the absence decision or infer a calendar update from a sent message.
| Destination | Required revision | Acknowledged |
|---|---|---|
| Team calendar | R2 | R2 |
| Reception calendar | R2 | R1 |
Match each destination acknowledgement
- Read approved LV2/R2
- Compare destination revision IDs
- Request reception R2 propagation
- Close on both R2 acknowledgements
A delayed R1 acknowledgement cannot overwrite a recorded R2 destination state.
How many destinations match and remain open?
Show the worked answer
One matches and one remains open. The approved source is R2 throughout; reception still needs R2 acknowledgement.
Keep the stale destination open
| Case | Action or result | Evidence boundary |
|---|---|---|
| Message sent to reception | Keep propagation pending | No R2 acknowledgement |
| Reception later acknowledgesR2 | Both destinations matched | Closure evidence supplied |
Retain per-destination revision and receipt references. One global “synced” label would conceal which copy is stale.