Historia awarii Rebuy

1. 1 września 2026 15:34 UTCinvestigating

   Obecnie badamy problemy z nawigacją w portalu administracyjnym Rebuy. Cała funkcjonalność na miejscu pozostaje nietaktowana.

2. 1 września 2026 15:43 UTCmonitoring

   Zastosowano rozwiązanie i wydaje się, że kwestie nawigacji zostały rozwiązane. Testujemy i monitorujemy, aby potwierdzić brak dalszych skutków.

3. 1 września 2026 15:50 UTCresolved

   Wszystkie zgłoszone problemy z nawigacją zostały rozwiązane.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 24 lipca 2026 07:06 UTCinvestigating

   Obecnie badamy problem z użytkownikami, którzy nie mają dostępu do konsoli admin. Wszystkie funkcje na miejscu pozostają funkcjonalne.

2. 24 lipca 2026 07:59 UTCinvestigating

   Nadal badamy tę kwestię.

3. 24 lipca 2026 08:20 UTCinvestigating

   Kontynuujemy śledztwo w sprawie dostępu do portalu. Zidentyfikowaliśmy również, że oferty po zakupie nie są prawidłowo renderowane dla niektórych sklepów. Nasz zespół aktywnie bada również tę sprawę i udostępni jej aktualizacje, gdy dowiemy się więcej.

4. 24 lipca 2026 08:25 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

5. 24 lipca 2026 08:29 UTCmonitoring

   Zastosowano rozwiązanie. Widzimy teraz przywrócony dostęp do administracji i oferty po zakupie prawidłowo renderując na uderzonych stronach, o których wiemy. Obecnie monitorujemy, aby zapewnić stabilność.

6. 24 lipca 2026 08:35 UTCresolved

   Wszystkie testy wykazują pozytywne wyniki i potwierdzamy, że te kwestie zostały rozwiązane. Będziemy kontynuować śledztwo w sprawie przyczyny i będziemy kontynuować sekcję zwłok po jej zakończeniu.

7. 24 lipca 2026 16:19 UTCpostmortem

   Co się stało? 24 lipca, między 2: 35 rano a 4: 28 rano ET, nasz portal administracyjny był krótko niedostępny, a Post- Zakup Oferty nie były renderowania dla kupców za pomocą tej funkcji. Występowało to w ciągu nocy podczas rutynowej konserwacji systemu. Twój sklep, checkout i wszystkie widżety na miejscu i zalecenia nadal funkcjonowały normalnie w całym tym oknie. Było to ograniczone do portalu administracyjnego i powierzchni oferty po zakupie. Uzasadnienie * * Root cause: * * W ramach naszej regularnej konserwacji, okresowo czyścimy starsze, niewykorzystane wersje naszego wewnętrznego oprogramowania, aby utrzymać wszystko działa skutecznie. Podczas jednego z tych rutynowych sprzątania, proces odniósł się nieco przestarzały migawki tego, co było obecnie żywe, a nie najbardziej aktualne wersji. Doprowadziło to do utrzymania starszej wersji zamiast obecnej. Ponieważ w międzyczasie systemy dotknięte problemem nadal działały na wersjach buforowych, nie miało to bezpośredniego wpływu. Kwestia ta stała się widoczna dopiero kilka godzin później, kiedy systemy te były poddawane cyklom w ramach normalnych operacji. Rozdzielczość Po zidentyfikowaniu, nasz zespół wrócił do służby, cofając się do ostatniej znanej dobrej wersji, rozwiązując problem. Następnie ponownie opublikowaliśmy bieżącą wersję, aby w pełni zakończyć sprawy i aktywnie sprawdzić nasze inne systemy wewnętrzne, aby potwierdzić wszystko inne działał zgodnie z oczekiwaniami. * * What we 're doing to prevent this from happing again: * * * Aktualizacja naszego procesu czyszczenia, aby zawsze odnosić się do wersji na żywo, uruchomiony w czasie rzeczywistym, a nie migawki wykonane wcześniej. Już sprawdziliśmy tę poprawę. * Dodanie wcześniej zautomatyzowane alarmowanie, aby nasz zespół mógł złapać i rozwiązać tego typu problem jeszcze szybciej w przyszłości. * Kontynuowanie wzmacniania naszych wewnętrznych narzędzi, więc rutynowa konserwacja jest jeszcze bardziej niezawodna idąc naprzód.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 22 lipca 2026 23:30 UTCinvestigating

   Obecnie badamy problem z użytkownikami, którzy nie mają dostępu do konsoli admin. Wszystkie funkcje na miejscu pozostają funkcjonalne.

2. 22 lipca 2026 23:46 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 22 lipca 2026 23:53 UTCresolved

   Incydent został rozwiązany. Przejrzymy dzienniki i przygotujemy sekcję zwłok, gdy będziemy mieć odpowiednie szczegóły.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 14 lipca 2026 17:21 UTCinvestigating

   Zdajemy sobie sprawę, że niektórzy kupcy doświadczają problemu, w którym komercyjne widżety i budujący pakiety nie są renderowane na ich sklepach. Nasz zespół aktywnie bada i pracuje nad naprawą. Ta kwestia nie dotyczy wszystkich kupców, i podzielimy się aktualizacją, jak tylko będziemy mieć więcej informacji.

2. 14 lipca 2026 17:31 UTCinvestigating

   Nadal aktywnie badamy problem z ładowaniem widżetów, który dotyczy niektórych stron handlowych. Nasz zespół zidentyfikował prawdopodobny czynnik i skupia się na tym teraz.

3. 14 lipca 2026 17:43 UTCmonitoring

   Zaimplementowano fix dla problemu obciążenia widget. Strony, które wcześniej zgłaszały błędy już ich nie widzą, a widżety i budujący pakiety są renderowania zgodnie z oczekiwaniami. Nasz zespół nadal sprawdza stabilność.

4. 14 lipca 2026 17:49 UTCresolved

   Wszystkie kwestie zostały rozwiązane. Widgets i bull budowniczych w obrębie dotkniętych stron są renderowania normalnie. Nasz zespół bada przyczynę i opublikuje aktualizację, jak tylko będzie dostępna.

5. 15 lipca 2026 15:19 UTCpostmortem

   Co się stało? 14 lipca rutynowa aktualizacja sposobu, w jaki jeden z naszych systemów odzyskuje informacje o produkcie spowodowała problem renderowania widżetów sklepowych na podzbiorze stron handlowych. Jeśli Twoje konto używa widżetów z tag- oparte zasady, takie jak cross-sell rekomendacje lub Bundle Builder, można zauważyć widżety nie ładowanie, lub produkty znikające po stronie załadowane. Ten problem nie ma wpływu na zameldowanie, admin, ani żadnych nie widget części sklepu. * * Root cause * * Dane znacznika produktu są przechowywane w dwóch różnych formatach za kulisami, w formacie dotychczasowym i nowszym, w zależności od tego, kiedy i jak pierwotnie został utworzony katalog produktów sklepu. Aktualizacja zmieniła ścieżkę używaną przez nasz system do pobierania danych dla widżetów, a ta ścieżka nie przekształciła nowszego formatu w format, jakiego oczekuje nasz kod widget. Na kontach, gdzie znaczniki produktów były przechowywane w nowszym formacie, kod widget nie mógł przetwarzać danych prawidłowo, co spowodowało problemy renderowania opisane powyżej. * * Resolution * * Odwróciliśmy aktualizację, która przywróciła normalny widget renderowania około 30 minut po rozpoczęciu problemu. Ponieważ niektóre dane widget są tymczasowo buforowane dla wydajności, niewielka liczba kont nadal widzieć nieregularne wyniki do czasu, że cache oczyszczone. Aktywnie odświeżyliśmy pamięć na wszystkich kontach. * * What we 're doing to prevent this of happing again * * * Przywracanie brakującego etapu konwersji danych i dodanie automatycznego testu, który sprawdza obie ścieżki wyszukiwania zawsze zwraca dopasowanie, poprawnie sformatowane dane zanim jakiekolwiek przyszłe wydanie może wyjść. * Budowa szybszego wewnętrznego narzędzia do odświeżania danych z pamięci podręcznej widget na kontach, więc jeśli podobny problem kiedykolwiek nastąpi ponownie, możemy rozwiązać pozostałość wpływ szybciej. * Realizowanie dwóch podstawowych formatów danych znaczników w jeden spójny format, aby usunąć tę klasę problemu u źródła, a nie tylko strzegąc przed nim w dół.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 lipca 2026 22:30 UTCinvestigating

   Zdajemy sobie sprawę, że niektórzy kupcy używający nieodziedziczonego Smart Cart doświadczają problemów z załadowaniem, a rodzimy koszyk zamiast tego ładuje. Nasz zespół aktywnie bada sprawę i pracuje nad sprawą. Podzielimy się informacjami, jak tylko dowiemy się więcej.

2. 7 lipca 2026 23:00 UTCinvestigating

   Nadal badamy tę kwestię.

3. 7 lipca 2026 23:11 UTCmonitoring

   Wskaźnik błędów spadł, a ładowanie Smart Cart wydaje się działać normalnie. Monitorujemy stabilność.

4. 7 lipca 2026 23:20 UTCresolved

   Ten incydent został zamknięty. Problem załadunku mający wpływ na niedziedziczny Smart Cart został rozwiązany, a my potwierdziliśmy stabilność w okresie monitorowania. Jeśli nadal będziecie widzieć jakieś problemy, proszę się odezwać i od razu się rozejrzymy.

5. 14 lipca 2026 17:55 UTCpostmortem

   * * Data incydentu: * * 7 lipca 2026 Czas trwania: * * Około 45 minut / Stan: Rozwiązane Podsumowanie 7 lipca, rutynowa aktualizacja skryptu krótko spowodowała, że Smart Cart nie otworzył dla części klientów w niektórych sklepach. Problem ten był raczej regionalny i przerywany, a nie pełen przerw, a normalna obsługa została przywrócona w ciągu około 45 minut. # Co się stało Podczas rutynowego rozmieszczania, mały podzbiór klientów załadował niedopasowaną parę plików skryptowych w zależności od ich lokalizacji i czasu. To spowodowało, że wózek nie inicjalizował dla nich. Po zidentyfikowaniu, cofnęliśmy zmianę i potwierdzone wózki były otwierane normalnie ponownie. # # Resolution Następnego dnia wysłaliśmy zabezpieczenie, aby zapobiec wpływowi tego konkretnego scenariusza na klientów, i przedstawiamy długoterminową aktualizację, w jaki sposób te pliki są modyfikowane, aby całkowicie to zakończyć.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 18 maja 2026 19:10 UTCinvestigating

   Rebuy is currently experiencing issues affecting admin and on-site functionality. Our team is aware and actively working on a resolution.

2. 18 maja 2026 19:16 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18 maja 2026 19:20 UTCmonitoring

   A fix has been implemented and we are seeing on-site and admin functionality return to normal. The team continues to monitor.

4. 18 maja 2026 19:29 UTCresolved

   The issue has been resolved. We will be investigating the root cause and sharing a post-mortem once our review is complete.

5. 20 maja 2026 15:05 UTCpostmortem

   **Incident Report: Admin and On-Site Functionality Disruption** **Date:** May 18, 2026 **Duration:** 3:10 PM – 3:29 PM ET \(~19 minutes\) **Summary** On May 18, 2026, merchants experienced a disruption affecting the Rebuy Admin Portal and on-site functionality including Smart Cart, Checkout Extensions, Post-Purchase Offers, A/B Testing, Smart Search, Smart Collections, and Rebuy Monetize. The issue was identified and resolved within 19 minutes. **Root Cause** The disruption was caused by a sequencing issue during a coordinated internal release. A database update that was required before new application code could safely serve traffic did not complete as expected. When the application code deployed and began serving requests, it encountered errors that cascaded across multiple product surfaces. **Resolution** We rolled back the affected services to the previous stable version within approximately 10 minutes of identifying the issue, which restored functionality for all merchants. The underlying database update was then completed successfully, and the full release was redeployed and verified shortly after. **What We're Doing** We are implementing additional verification gates in our multi-service release process to ensure that dependent infrastructure changes are confirmed live in production before downstream application code is allowed to deploy.

1. 12 maja 2026 17:10 UTCresolved

   A release to the Rebuy storefront SDK on 2026-05-11 introduced a regression for merchants who have the Rebuy app installed but do not have Smart Cart V2 active: clicks on their native Shopify cart icon stopped opening their theme's cart drawer.

2. 12 maja 2026 19:14 UTCpostmortem

   **Incident Report: Native Cart Regression** **Date:** May 11, 2026 **Duration:** 9:36 AM – 12:50 PM ET \(~3 hours 14 minutes\) **Summary** On May 11, 2026, a subset of merchants experienced an issue where the cart icon on their storefront was unresponsive to shoppers. The issue was introduced as part of a scheduled SDK release and was fully resolved within 18 minutes of being identified. **Root Cause** A performance update to the Rebuy storefront SDK introduced a change that inadvertently interfered with native cart behavior for merchants who do not have Smart Cart V2 enabled. Merchants with Smart Cart V2 active were not affected. **Resolution** Once identified, we reverted the SDK release within 18 minutes. Native cart functionality was restored immediately upon revert. **What We're Doing** We are expanding our pre-release testing coverage to ensure that SDK changes are validated across all merchant configurations before reaching production — including merchants who may not have specific Rebuy features enabled. We are also reinforcing our internal review process to include configuration-specific test cases as a required step before any storefront SDK release. These changes will help us catch unintended side effects earlier in the development cycle and prevent a similar disruption from reaching your store.

1. 22 kwietnia 2026 16:53 UTCinvestigating

   We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts.We have received multiple reports of Smart Cart loading inconsistently on some merchant storefronts. Our team is actively investigating and will provide updates as we learn more.

2. 22 kwietnia 2026 17:02 UTCinvestigating

   Our team continues to investigate. Current findings suggest the impact may vary by region.

3. 22 kwietnia 2026 17:06 UTCmonitoring

   A change has been deployed and merchants who reported issues are seeing improved results. We are continuing to investigate the root cause and will share more details as they become available.

4. 22 kwietnia 2026 17:18 UTCresolved

   This issue has been resolved. Our team is completing a full root cause analysis, which will be posted to the status page once available. Thank you for your patience.

5. 22 kwietnia 2026 19:19 UTCpostmortem

   **What happened:** On April 22, 2026, between approximately 11:45 AM and 1:02 PM ET, a subset of shoppers on Rebuy-powered storefronts experienced an inability to load SmartCart V2. Merchants and shoppers who encountered the issue during this window would have seen the cart fail to initialize. All other Rebuy functionality remained operational throughout the incident. ‌ **Duration:** Approximately 1 hour and 17 minutes. ‌ **Impact:** A subset of shoppers on affected storefronts were unable to load SmartCart V2 during the incident window. No data was lost or compromised. ‌ **What caused it:** A software release introduced changes that shifted internal script references in a way that caused the cart to fail for shoppers loading a fresh version of the storefront script during the deployment window. Shoppers with a cached version of the script were unaffected. ‌ **What we did:** Our team identified the issue within minutes of the first report, rolled back to the previous stable release, and confirmed full restoration of SmartCart V2 by 1:02 PM ET — approximately 16 minutes from first report to resolution. ‌ **What we are doing to prevent recurrence:** We have identified the root cause and are implementing structural improvements to our deployment pipeline, including additional validation steps to catch this class of issue before it reaches production.

1. 18 marca 2026 16:43 UTCinvestigating

   We are currently investigating not being able to access Rebuy Admin.

2. 18 marca 2026 17:00 UTCinvestigating

   This is only affecting admin accessibility and all on-site functionality is normal. We continue to investigate what is causing the errors with the admin platform.

3. 18 marca 2026 17:08 UTCmonitoring

   The issue has been identified, and a fix has been implemented.

4. 18 marca 2026 17:16 UTCresolved

   This incident has been resolved.

5. 18 marca 2026 20:24 UTCpostmortem

   **What happened** On March 18, 2026, between 12:25 PM and 1:05 PM ET, a security update to our PHP base image introduced a configuration change that caused Smart Cart, widgets, post-purchase flows, Rebuy Monetize offers, and the Admin dashboard to return errors for approximately 40 minutes. **Duration** Approximately 30-40 minutes. **What caused it** A routine infrastructure update introduced an unexpected configuration conflict that prevented our admin service from accepting traffic. Once identified, our team rolled back the update to restore full functionality. **What we did** Our team identified the issue, implemented a rollback, and confirmed full resolution within the same hour. We posted updates to our status page throughout the incident. **What we are doing to prevent recurrence** We have identified the root cause and are implementing additional validation steps in our deployment process to catch this class of issue before it reaches production.

1. 5 marca 2026 22:15 UTCinvestigating

   We are currently investigating legacy carts not rendering, widgets, and data sources.

2. 5 marca 2026 22:21 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 5 marca 2026 22:32 UTCmonitoring

   A fix has been implemented, and we are monitoring results.

4. 5 marca 2026 22:42 UTCresolved

   This incident has been resolved, and everything is back to operational.

5. 6 marca 2026 15:38 UTCpostmortem

   **Description:** On March 5th, between 4:58 PM and 5:20 PM EST, merchants may have experienced issues accessing certain areas of the Rebuy Admin. Affected areas included Data Source configuration, Smart Cart V1, and Admin Settings. The disruption lasted approximately 20 minutes. No storefront disruptions occurred for active merchants and no data was lost or corrupted. **Root Cause:** A scheduled security update introduced an incorrect configuration change during our release process, causing the affected Admin areas to become unavailable. **Resolution:** Our engineering team identified the root cause immediately after deployment and deployed a targeted fix, restoring full service by 5:20 PM EST. **Next Steps:** We are adding additional validation steps to our release process to prevent this class of error from reaching production in the future.

1. 4 marca 2026 18:49 UTCresolved

   Description On February 24th at 3:11 PM EST, a code change was deployed as part of a security improvement. The following morning at 8:35 AM EST, merchants began experiencing Shopify Checkout Extensions not rendering. Core checkout functionality remained operational and no data was lost or corrupted. Root Cause: The deployed change introduced a data shape update that was not reflected in the Checkout Extension schema, causing validation to fail during extension initialization and preventing extensions from rendering. Resolution: Our engineering team identified the mismatch and deployed a fix at 10:05 AM EST on February 25th, restoring full Checkout Extension functionality. Next Steps: Review and improve existing monitoring coverage for extension initialization failures to ensure alerts fire as expected. Additionally, introduce cross-functional review requirements for changes that touch shared data contracts to catch downstream impacts before deployment.

1. 18 lutego 2026 18:15 UTCinvestigating

   We're currently aware of an issue that may temporarily affect the ability to create new Smart Carts, Smart Flows, Widgets, Bundle Builder, Monetize or add new packages. Our team is actively working to resolve this as quickly as possible. All existing configurations and on-site tooling remain fully functional. No action is needed on your end. We'll provide an update once everything is back to normal. Thank you for your patience!

2. 18 lutego 2026 18:32 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18 lutego 2026 18:49 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18 lutego 2026 19:05 UTCresolved

   All tests are showing positive results. This issue has been resolved.

5. 19 lutego 2026 18:23 UTCpostmortem

   **Description:** On February 18th, between 12:44 PM and 1:44 PM EST, merchants may have experienced errors when attempting to create new configurations within the Rebuy platform. Affected actions included the creation of Smart Carts, Checkout Extension Widgets, Merchandising Widgets, Bundle Builder, Smart Flows, and Monetize Widgets. The disruption lasted approximately 60 minutes. Read operations and existing store configurations were not impacted, meaning no storefront disruptions occurred for active merchants, and no data was lost or corrupted. **Root Cause:** A planned platform deployment unintentionally introduced a dependency update that conflicted with how our system handles certain create and update operations, causing those requests to fail. **Resolution:** Our engineering team identified the root cause and deployed a targeted fix within the same deployment window, restoring full service by 1:44 PM EST.

1. 6 stycznia 2026 21:40 UTCresolved

   We experienced a brief issue where some users encountered an internal error message upon login, preventing access to the system. The team quickly identified and resolved the issue, with the total impact lasting approximately 6 minutes.

2. 8 stycznia 2026 20:09 UTCpostmortem

   **Description:** On January 6th at approximately 4:10 PM ET an update aimed at improving security caused a temporary disruption, affecting some user logins for approximately 6 minutes. The issue was linked to unexpected behavior in the system's connection to our Redis database, crucial for authentication. **Root Cause:** The update unintentionally allowed operations in production environments that were unnecessary, combined with temporary Redis connection issues, which impacted some user logins. **Resolution:** We reverted the changes to restore service stability. **Next Steps:** We are implementing additional safeguards and better error handling to prevent similar issues from arising in the future. We will then re-deploy the security change after the additional tests have been complete.

1. 22 grudnia 2025 17:12 UTCresolved

   On Dec 19, between approximately 6:19–8:55 AM ET, an upstream network provider experienced intermittent performance issues that led to unexpected errors and degraded performance for some users. The issue was identified, a fix was applied, and service was fully restored the same day after continued monitoring.

1. 5 grudnia 2025 15:47 UTCresolved

   A change made to one of our cloud providers Web Application Firewall (WAF) parsing logic led to an unexpected network outage for several minutes on the morning of Dec 5. During this time, there were reports of 500 internal server errors when attempting to access the Rebuy platform. It lasted for approximately 15 minutes. The issue was resolved once the fix was implemented and the network returned to normal. Ongoing monitoring was conducted to ensure stability. There are no further issues at this time

1. 18 listopada 2025 12:32 UTCinvestigating

   We are currently impacted by an outage that our cloud provider is experiencing. We are seeing some services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts. The team is working on the issue and we will relay any information that we get as we get it. Thank you for your patience.

2. 18 listopada 2025 12:47 UTCinvestigating

   We are still encountering intermittent errors. The team continues the investigation and remediation efforts.

3. 18 listopada 2025 13:12 UTCidentified

   The provider has just announced that the issue has been identified and a fix is underway. We are seeing things beginning to stabilize on our monitoring.

4. 18 listopada 2025 13:15 UTCmonitoring

   They have implemented the fix and we are now seeing pre-outage performance return. We are monitoring for further updates.

5. 18 listopada 2025 13:18 UTCmonitoring

   The cloud provider has identified the issue and restored service. All systems are operational. Continuing to monitor.

6. 18 listopada 2025 13:56 UTCresolved

   Our third-party provider has confirmed that the issue is identified and fully resolved, and our systems are operating normally. We are no longer seeing any related errors or service impact. We are working with the provider to understand the root cause and will share a post-mortem as soon as it becomes available.

1. 29 października 2025 18:24 UTCinvestigating

   Our team has identified an increase in errors within the Rebuy administrative portal, and some users are experiencing login issues. We are actively investigating the cause. All on-site functionality with Rebuy features remains unaffected. Further updates will follow shortly.

2. 29 października 2025 18:32 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 29 października 2025 18:35 UTCmonitoring

   A fix has been implemented and we are seeing the errors subside and admin functionality is back online.

4. 29 października 2025 18:47 UTCresolved

   The issues affecting the Rebuy administrative portal have been resolved. Users should now be able to log in and access all functionality without errors. Our team is conducting a review of the incident and will share a post-mortem once completed. Thank you for your patience.

5. 5 listopada 2025 14:18 UTCpostmortem

   **Incident Summary:** On October 29, 2025, some users experienced an outage of the Rebuy Engine admin system starting around 12:15 MST, which lasted for approximately 24 minutes. The impact of the outage was users were unable to login to the system - all on-site functionality remained stable. Initially, there were concerns that the issue might be related to the release of updates earlier in the day. However, further investigation revealed that the cause was more complex and not directly tied to the code release. ‌ **Root Cause:** The disruption in the admin system was the result of a combination of infrastructure and process-related factors that temporarily impacted performance. During the event, certain system components experienced reduced efficiency under load, which contributed to intermittent connectivity issues and overall degradation. ‌ **Resolution:** The issue was resolved as connectivity stabilized and the system returned to normal operations. We have taken steps to ensure the system is now functioning as expected, and further monitoring will be in place to prevent similar disruptions in the future. ‌ **Preventive Measures:** To avoid similar issues going forward, we will: * Improve monitoring and resource management to ensure smoother handling of system load. * Conduct additional internal reviews to optimize system performance and enhance reliability.

1. 27 października 2025 17:49 UTCidentified

   Some customers are seeing issues concerning Smart Cart not loading properly. Our team is aware and working on a solution.

2. 27 października 2025 17:52 UTCmonitoring

   A fix has been implemented and the errors have subsided. We are monitoring for any further issues.

3. 27 października 2025 17:57 UTCresolved

   The incident has been resolved and the impacted carts are confirmed functional once again. Our team will investigate the root cause and share the findings in this incident once available. Thank you for your patience.

4. 28 października 2025 19:40 UTCpostmortem

   **Incident Summary:** On October 27, 2025, some merchants experienced an issue where their Smart Cart failed to open. This occurred shortly after the release of a new feature designed to support _nested cart items_ in Smart Cart V2. The feature enables merchants to display parent-child product relationships \(such as bundles or configurable products\) directly within the Smart Cart, improving consistency between the cart and checkout experience. ‌ **Root Cause:** The issue stemmed from a missing optionality check in the new nested cart item functionality. The shared cart file \(`Cart.js`\) is used by both Smart Cart V1 and V2. The new code called a function, `nestedCartItemsEnabled()`, that only exists in V2. Because this function does not exist in V1, the call caused a JavaScript error that prevented the Smart Cart from loading for merchants still using the legacy version. ‌ **Resolution:** A fix was implemented by adding an optionality check to ensure the function is only executed when present. This change restored functionality for all merchants using Smart Cart V1, while maintaining the new nested cart item capability for V2. The fix was verified locally and across multiple staging environments using different Smart Cart configurations prior to implementation. ‌ **Preventive Measures:** * Added an additional safeguard to confirm version-specific functions are handled appropriately in shared code. * Updated internal review processes to ensure smoother compatibility between Smart Cart versions.

1. 16 października 2025 16:33 UTCinvestigating

   We are aware of an ongoing issue with double add-to-cart events in Smart Cart that we reported on last week, which may still be affecting some users. Our team is actively investigating this further to find a permanent solution. In the meantime, we have identified a temporary workaround that can be implemented within your Smart Cart settings. If you're experiencing double add-to-cart events when adding a single product to your cart, please follow the steps below based on your version of Smart Cart: For New Carts (v2): 1. Go to your Smart Cart. 2. Click "Global Settings" at the bottom of the page. 3. Locate the "Product Form Submission Behavior" setting and change it to "Disabled (Smart Cart does not manage)." 4. Refresh your product page and test to confirm the issue is resolved. For Legacy Smart Carts: 1. Go to your Smart Cart. 2. Scroll down to find the "Product Form Redirect" setting and change it to "Disabled (Smart Cart does not manage)." 3. Refresh your product page and test to confirm the issue is resolved. For more details on the previously reported issue, please visit: https://status.rebuyengine.com/incidents/ddkm5p8xgb7c We will continue to work the situation and provide updates as soon as possible. We sincerely apologize for any inconvenience this may have caused and appreciate your patience as we work toward a resolution.

2. 16 października 2025 18:13 UTCmonitoring

   We’ve successfully tested and deployed a solution to prevent the duplicate add-to-cart (ATC) events from occurring. Our team has verified the fix with several stores that reported the issue, and we can confirm that it’s no longer happening. We will continue monitoring the situation over the next few hours to ensure everything is running smoothly. If you notice any unusual behavior, please notify our support team immediately.

3. 16 października 2025 19:17 UTCmonitoring

   We are continuing to monitor for any further issues. None have been reported or uncovered through testing at this time.

4. 16 października 2025 19:45 UTCresolved

   The incident has been resolved. Our team will document the root cause and share the findings in this incident once available.

5. 17 października 2025 14:10 UTCpostmortem

   **Issue Overview:** Recently, some merchants experienced an issue where products were being added to the cart twice instead of once. This was caused by a conflict between Rebuy’s Smart Cart and the code in your Shopify theme. When both systems tried to handle the form submission at the same time, it resulted in duplicate items being added. ‌ **Why It Happened:** This issue started happening after a recent update to Shopify themes around October 10, 2025. While the issue didn’t affect all merchants, it did impact those with certain theme setups or third-party apps interacting with the cart. ‌ **Resolution Timeline:** * **Saturday 10/11:** Code update deployed to fix the double-add issue, but caused a secondary issue with Smart Cart not opening. * **Sunday 10/12:** Follow-up fix resolved the Smart Cart opening issue. Both problems were considered resolved. * **Monday 10/13 - Thursday 10/16:** Continued monitoring of the issue, with sporadic reports of duplicate ATC events. A temporary workaround was made available to merchants, and we tested the fix on multiple environments. * **Thursday, 10/16:** Final fix deployed to address the root cause and ensure compatibility with the Shopify theme update. Since this deployment, there have been no further reports of duplicate add-to-cart issues. **What the Fix Does:** The new solution ensures that if a product is added to the cart multiple times, the system will catch and remove any extra items. This prevents duplicate purchases and ensures the cart reflects the correct quantity. Importantly, this fix will work whether or not Shopify resolves the issue on their end, so there is no risk of the fix causing other problems. ‌ **Warning Message:** If this issue happens again, a warning message will appear, prompting you to adjust the Smart Cart settings. It will explain that there’s a conflict between Rebuy and the theme’s code and guide you on how to change the Product Form Redirect setting in Global Settings to "Disabled." ‌ **Next Steps with Shopify:** We’re working closely with Shopify to understand what triggered this issue and to improve communication on future theme updates. This will help us identify and resolve potential conflicts proactively. We’re also testing future theme updates in staging environments to catch any issues before they affect merchants.

1. 15 października 2025 16:41 UTCinvestigating

   We are currently experiencing some technical difficulties. The team is aware and investigating.

2. 15 października 2025 16:46 UTCidentified

   The team believes that they have uncovered the issue and are currently taking steps to resolve.

3. 15 października 2025 16:51 UTCmonitoring

   A fix has been implemented and we are starting to see issues resolving. We are monitoring to ensure stability.

4. 15 października 2025 16:57 UTCresolved

   The incident has been resolved. Our team will investigate the root cause and share the findings in this incident once available.

5. 16 października 2025 19:03 UTCpostmortem

   **Incident Summary:** On October 15, 2025, users experienced a temporary outage beginning around 12:30 PM EDT. During this period, the site was unavailable and requests returned error messages. **Root Cause:** The outage occurred as part of a planned upgrade to our PHP platform. Certain default configuration settings in the new environment were incompatible with our existing application setup, which prevented the system from starting correctly. Once identified, these configurations were adjusted and service was restored. **Preventive Measures:** We’ve updated our deployment and validation processes to better account for these types of environment-specific configuration differences during future upgrades. There is no ongoing risk or further impact is expected.