Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
DG38 · Expired or changed campaign cannot reuse approval
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual · concurrency/retry rehearsal |
| Priority | — |
| Gates | S12, S13 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q24, Q14, Q16 |
Given
Approved promotion has content revision, channel, audience and validity; price changes or expiry precedes posting; staff retries.
When
Run final check and duplicate-activity check before each simulated send/post.
Then / oracle
New terms/copy/recipient/channel/period require current permission; hold stale/expired work. One actual placement is not counted twice; reconcile ambiguous send before retry. No automatic posting feature claimed.
Evidence required
Approved versus final payload/hash, check time, hold/reconciliation and one activity/placement evidence.
Decision dependency (verbatim)
Q24/Q14/Q16: approval granularity, scheduling and manual duplicate handling.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.