42 lines
1.2 KiB
Markdown
42 lines
1.2 KiB
Markdown
---
|
|
date: 2026-08-11
|
|
jira: TECH-32582
|
|
actual_sync_issue: false
|
|
status: investigating
|
|
classification:
|
|
---
|
|
|
|
# TECH-32582
|
|
## Observation
|
|
|
|
- Promo non mises en ligne
|
|
|
|
## Verification
|
|
|
|
- Reported time:
|
|
- Checked time:
|
|
- Expected availability:
|
|
- Content available:
|
|
- Technical issue identified:
|
|
|
|
## Outcome
|
|
|
|
-
|
|
|
|
---
|
|
|
|
Available status:
|
|
- investigating
|
|
- resolved
|
|
- monitoring
|
|
|
|
Available classifications
|
|
|
|
| Classification | Use when |
|
|
| ---------------------- | ---------------------------------------------------------------------------------- |
|
|
| `confirmed-sync-issue` | There was an actual technical synchronization problem |
|
|
| `no-issue-confirmed` | Complaint resolved/no technical issue found |
|
|
| `unrelated-issue` | The problem was real, but **not caused by synchronization** |
|
|
| `user-error` | Incorrect action/configuration/input by the requester caused the perceived problem |
|
|
| `unknown` | Insufficient information to determine what happened |
|