[MAGNOLIA-9144] Magnolia randomly serves an old version of an asset after performing changes on it Created: 16/Oct/23 Updated: 10/Jan/24 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | cache |
| Affects Version/s: | 6.2.39 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roberto Gaona | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: | |||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Epic Link: | AuthorX Support | ||||
| Team: | |||||
| Description |
|
This issue is strange when it comes to reproducing it, since it doesn't affect all users the same way. It's reproducible on both Mac using Firefox and Windows, using both Firefox and Chrome. The steps to reproduce this issue are as it follows (on demo-author):
It looks like a possible browser issue, but the fact that it can't be reproduced constantly even using the same browser version on different devices made it a pain to test. |