vault backup: 2026-08-19 16:34:54
This commit is contained in:
@@ -14,7 +14,7 @@
|
|||||||
|
|
||||||
## Significant Events
|
## Significant Events
|
||||||
|
|
||||||
-
|
- Document contractuel refusé par Wp-Expert
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|||||||
@@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
date:
|
||||||
|
jira:
|
||||||
|
actual_sync_issue: false
|
||||||
|
status: investigating
|
||||||
|
classification:
|
||||||
|
project: "[[Idello]]"
|
||||||
|
---
|
||||||
|
|
||||||
|
# TECH-32615
|
||||||
|
## Observation
|
||||||
|
|
||||||
|
```
|
||||||
|
Nous avons remarqué que parfois des mises à jour éditoriales ou en lien avec la programmation ne se reflétaient pas sur le site à la synchronisation suivante, ni même après plusieurs synchros.
|
||||||
|
|
||||||
|
- Notamment, il n’est pas rare que des épisodes arrivent dissociés d'une collection sur IDÉLLO.
|
||||||
|
Ex 1 :
|
||||||
|
- gp264265
|
||||||
|
- gp264267
|
||||||
|
- gp264269
|
||||||
|
- gp264271
|
||||||
|
- gp264272
|
||||||
|
- gp264275
|
||||||
|
- gp264277
|
||||||
|
|
||||||
|
Dissociés de la collection 002701362.
|
||||||
|
|
||||||
|
- Ex 2 :
|
||||||
|
- gp196483
|
||||||
|
|
||||||
|
Seul épisode dissocié de la collection 002391091.
|
||||||
|
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
## 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 |
|
||||||
Reference in New Issue
Block a user