Uscreen experienced a minor incident on June 19, 2024 affecting Storefront, lasting 1h 6m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 19, 2024, 05:07 PM UTC
🔎 Investigating: We are currently looking into an issue where videos are not loading from the catalog on the web. Thank you for your patience as we look into resolving this issue.
- identified Jun 19, 2024, 05:30 PM UTC
We've identified the root cause of the issue and are preparing a quick fix. Thank you for your continued patience.
- monitoring Jun 19, 2024, 05:33 PM UTC
A fix has been implemented and videos should now be loading properly. We'll continue to monitor.
- monitoring Jun 19, 2024, 05:34 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 19, 2024, 06:14 PM UTC
This issue has been resolved. Thank you for your patience.
- postmortem Jun 19, 2024, 07:04 PM UTC
We wanted to provide a detailed postmortem of the issue that occurred on June 17th, affecting video loading on the web. ### **Summary of the Issue** Our investigation began at 17:07 UTC and was resolved by 18:14 UTC. During this period, you may have experienced problems with videos not loading properly from the catalog. ### **Timeline of Events** 1. **17:07 UTC - Investigating:** We began investigating reports of videos not loading from the catalog on the web. 2. **17:30 UTC - Identified:** We identified the root cause as a recent deployment, which included a feature condition that erroneously caused redirects when users clicked on videos, redirecting them back to the catalog. 3. **17:33 UTC - Monitoring:** A fix was implemented, and videos began loading properly. We continued to monitor for any further issues. 4. **18:14 UTC - Resolved:** The issue was fully resolved. ### **Root Cause and Resolution** The problem was traced to a deployment today that included a feature condition for redirects. This condition mistakenly caused redirects back to the catalog when end-users clicked on videos. Our team quickly identified and implemented a patch to fix the redirect issue. ### **Preventive Measures** To prevent similar issues in the future, we will ensure all redirect features are applied with proper feature flagging. This will help avoid erroneous redirects and ensure smoother deployment processes. We apologize for any inconvenience this issue may have caused. Your patience and understanding are greatly appreciated.