75 lines
2.1 KiB
Markdown
75 lines
2.1 KiB
Markdown
---
|
||
date: 2026-08-19
|
||
jira: TECH-32615
|
||
actual_sync_issue: true
|
||
status: resolved
|
||
classification: confirmed-sync-issue
|
||
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:
|
||
|
||
p1-synccms-02 ne marchait pas bien. Les supervisors étaient en mode Fatal et refusé de se relancer.
|
||
Les commandes php artisan ne marchait pas non plus.
|
||
|
||
Solution fut d'effacer les cache avec la commande
|
||
```php
|
||
rm -f bootstrap/cache/config.php bootstrap/cache/services.php bootstrap/cache/packages.php
|
||
php artisan config:clear
|
||
```
|
||
|
||
Ceci permet de relancer les services supervisor
|
||
## Outcome
|
||
|
||
- Les prochaines sync devraient fonctionner correctement
|
||
|
||
---
|
||
|
||
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 |
|