Historial de interrupciones de Rebuy

1. September 1, 2026 at 3:34 PM UTCinvestigating

   Actualmente estamos investigando cuestiones con la navegación dentro del portal Rebuy admin. Toda la funcionalidad in situ permanece en contacto en este momento.

2. September 1, 2026 at 3:43 PM UTCmonitoring

   Se ha aplicado una solución y las cuestiones de navegación parecen haberse resuelto. Estamos probando y monitorizando para confirmar que no hay más impacto.

3. September 1, 2026 at 3:50 PM UTCresolved

   Todas las cuestiones de navegación comunicadas se han resuelto en este momento.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 7:06 AM UTCinvestigating

   Actualmente estamos investigando un problema con los usuarios que no pueden acceder a la consola de administración. Toda la funcionalidad in situ sigue siendo funcional.

2. July 24, 2026 at 7:59 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 24, 2026 at 8:20 AM UTCinvestigating

   Continuamos investigando los problemas de acceso al portal de administración. También hemos identificado que las ofertas de post-purchase no están renderizando correctamente para algunas tiendas. Nuestro equipo también está investigando esto activamente y compartirá actualizaciones a medida que aprendamos más.

4. July 24, 2026 at 8:25 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. July 24, 2026 at 8:29 AM UTCmonitoring

   Se ha aplicado una solución. Ahora estamos viendo el acceso de administrador restaurado y post-purchase ofrece renderizar correctamente en los sitios impactados que somos conscientes. Estamos monitoreando para asegurar la estabilidad en este momento.

6. July 24, 2026 at 8:35 AM UTCresolved

   Todas las pruebas muestran resultados positivos y estamos confirmando estos problemas como resueltos en este momento. Seguiremos investigando la causa raíz y seguiremos con un post mortem una vez que esté completo.

7. July 24, 2026 at 4:19 PM UTCpostmortem

   ¿Qué pasó? El 24 de julio, entre aproximadamente las 2:35 AM y 4:28 AM ET, nuestro portal de administración fue brevemente indisponible, y las ofertas de Post-Purchase no estaban rindiendo a los comerciantes usando esa característica. Esto ocurrió de la noche a la mañana durante el mantenimiento del sistema de rutina. Su escaparate, checkout y todos los widgets y recomendaciones del sitio continuaron funcionando normalmente a través de esta ventana. Esto se limitó al portal de administración y la superficie de oferta post-purchase. **Causa principal:** Como parte de nuestro mantenimiento regular, periódicamente limpiamos versiones antiguas y no utilizadas de nuestro software interno para mantener las cosas funcionando eficientemente. Durante una de estas limpiezas rutinarias, el proceso hizo referencia a una instantánea ligeramente anticuada de lo que actualmente estaba vivo, en lugar de la versión más actualizada. Esto le llevó a retener una versión anterior en lugar de la actual. Dado que los sistemas afectados continuaron funcionando en versiones en caché mientras tanto, no hubo ningún impacto inmediato. El problema sólo se hizo visible varias horas más tarde, cuando esos sistemas se cicló como parte de operaciones normales. Resolución Una vez identificado, nuestro equipo restableció el servicio volviendo a la última versión conocida, resolviendo el problema. Luego reeditamos la versión actual para cerrar completamente las cosas y revisar proactivamente nuestros otros sistemas internos para confirmar que todo lo demás estaba funcionando como se esperaba. *Lo que estamos haciendo para evitar que esto vuelva a suceder* * Actualizando nuestro proceso de limpieza para siempre referenciar la versión en vivo, en tiempo real, en lugar de una instantánea tomada antes. Ya hemos probado esta mejora con éxito. * Añadiendo alerta automatizada anterior para que nuestro equipo pueda atrapar y resolver este tipo de problema aún más rápido en el futuro. * Seguir fortaleciendo nuestra herramienta interna para que el mantenimiento rutinario como este sea aún más fiable.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 11:30 PM UTCinvestigating

   Actualmente estamos investigando un problema con los usuarios que no pueden acceder a la consola de administración. Toda la funcionalidad in situ sigue siendo funcional.

2. July 22, 2026 at 11:46 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 22, 2026 at 11:53 PM UTCresolved

   El incidente se ha resuelto. Revisaremos los registros y prepararemos un post mortem una vez tengamos los detalles apropiados.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 14, 2026 at 5:21 PM UTCinvestigating

   Somos conscientes de que algunos comerciantes están experimentando un problema donde los widgets merchandising y los constructores de paquetes no están rindiendo en sus escaparates. Nuestro equipo está investigando y trabajando activamente para una solución. Este problema no afecta a todos los comerciantes, y compartiremos una actualización tan pronto como tengamos más información.

2. July 14, 2026 at 5:31 PM UTCinvestigating

   Todavía estamos investigando activamente el problema de carga de widget que afecta a algunos sitios mercaderes. Nuestro equipo ha identificado un factor que probablemente contribuya y se está centrando en eso ahora.

3. July 14, 2026 at 5:43 PM UTCmonitoring

   Se ha implementado una solución para el problema de carga de widget. Los sitios que anteriormente reportaban errores ya no los están viendo, y los widgets y constructores de paquetes están renderizando como se espera. Nuestro equipo sigue probando la estabilidad.

4. July 14, 2026 at 5:49 PM UTCresolved

   Todas las cuestiones se han resuelto en este momento. Los Widgets y constructores de paquetes en los sitios afectados están renderizando normalmente. Nuestro equipo está investigando la causa raíz y publicará una actualización tan pronto como esté disponible.

5. July 15, 2026 at 3:19 PM UTCpostmortem

   ¿Qué pasó? El 14 de julio, una actualización rutinaria de cómo uno de nuestros sistemas recupera información de producto causó un problema de renderización para los widgets de almacén en un subconjunto de sitios de comerciantes. Si su cuenta utiliza widgets con reglas basadas en etiquetas, tales como recomendaciones cross-sell o Bundle Builder, puede haber notado widgets que no cargan, o productos que desaparecen después de la página cargada. Este problema no afectó el checkout, el administrador, ni ninguna parte de su escaparate. *Causa de raíz* Los datos de etiquetas de producto se almacenan en dos formatos diferentes detrás de las escenas, un formato legado y uno nuevo, dependiendo de cuándo y cómo se creó originalmente el catálogo de productos de una tienda. La actualización cambió el camino que nuestro sistema utiliza para recuperar esos datos para widgets, y ese camino no convirtió el nuevo formato en el formato que nuestro código widget espera. En las cuentas donde se almacenaban etiquetas de producto en el formato más nuevo, el código widget no podía procesar los datos correctamente, lo que causó los problemas de renderización descritos anteriormente. **Resolución** Revertimos la actualización, que restauró el widget normal renderizando unos 30 minutos después del inicio del problema. Debido a que algunos datos de widget están temporalmente preparados para el rendimiento, un pequeño número de cuentas siguió viendo resultados de estancamiento hasta que ese caché se limpió. Actualizamos proactivamente el caché en todas las cuentas afectadas. Lo que estamos haciendo para evitar que esto suceda de nuevo * Restaurar el paso de conversión de datos perdidos y agregar una prueba automatizada que comprueba ambos caminos de recuperación siempre devuelve datos coincidentes, correctamente formateados antes de que cualquier futura versión pueda salir. * Construir una herramienta interna más rápida para actualizar los datos de widget caché a través de las cuentas, por lo que si un problema similar ocurre de nuevo, podemos resolver el impacto residual más rápidamente. * Reconciliar los dos formatos de datos de etiquetas subyacentes en un solo formato consistente, para eliminar esta clase de problema en la fuente en lugar de sólo protegerse contra ella aguas abajo.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 7, 2026 at 10:30 PM UTCinvestigating

   Somos conscientes de que algunos comerciantes que usan Smart Cart no-legado están experimentando problemas de carga y el carrito nativo está cargando en su lugar. Nuestro equipo está investigando activamente la causa y trabajando en una solución. Compartiremos una actualización tan pronto como sepamos más.

2. July 7, 2026 at 11:00 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 7, 2026 at 11:11 PM UTCmonitoring

   Las tasas de error han bajado y la carga Smart Cart parece estar funcionando normalmente de nuevo. Estamos monitoreando para la estabilidad.

4. July 7, 2026 at 11:20 PM UTCresolved

   Este incidente está cerrado. Se ha resuelto el problema de carga que afecta a Smart Cart, y hemos confirmado la estabilidad durante el período de monitoreo. Si sigues viendo cualquier problema, por favor contacta y echaremos un vistazo de inmediato.

5. July 14, 2026 at 5:55 PM UTCpostmortem

   **Fecha de identificación:** 7 de julio de 2026 *Duración* aprox. 45 minutos **Status:** Resolved ## Summary El 7 de julio, una actualización de script de rutina causó brevemente que Smart Cart no se abrira para una parte de los compradores en algunas tiendas. El tema era regional e intermitente en lugar de una salida completa, y el servicio normal fue restaurado en unos 45 minutos. ## What Happened Durante un despliegue de rutina, un pequeño subconjunto de compradores cargaba un par de archivos de script desajustados dependiendo de su ubicación y momento. Esto causó que el carrito no inicializara para ellos. Una vez identificados, volamos el cambio y los carros confirmados estaban abriendo normalmente de nuevo. Resolución Enviamos una salvaguardia al día siguiente para evitar que este escenario específico afecte a los compradores hacia adelante, y estamos preparando una actualización a más largo plazo de cómo estos archivos están versionados para cerrar esto completamente.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 18, 2026 at 7:10 PM UTCinvestigating

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

2. May 18, 2026 at 7:16 PM UTCidentified

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

3. May 18, 2026 at 7:20 PM UTCmonitoring

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

4. May 18, 2026 at 7:29 PM UTCresolved

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

5. May 20, 2026 at 3:05 PM 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. May 12, 2026 at 5:10 PM 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. May 12, 2026 at 7:14 PM 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. April 22, 2026 at 4:53 PM 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. April 22, 2026 at 5:02 PM UTCinvestigating

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

3. April 22, 2026 at 5:06 PM 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. April 22, 2026 at 5:18 PM 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. April 22, 2026 at 7:19 PM 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. March 18, 2026 at 4:43 PM UTCinvestigating

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

2. March 18, 2026 at 5:00 PM 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. March 18, 2026 at 5:08 PM UTCmonitoring

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

4. March 18, 2026 at 5:16 PM UTCresolved

   This incident has been resolved.

5. March 18, 2026 at 8:24 PM 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. March 5, 2026 at 10:15 PM UTCinvestigating

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

2. March 5, 2026 at 10:21 PM UTCidentified

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

3. March 5, 2026 at 10:32 PM UTCmonitoring

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

4. March 5, 2026 at 10:42 PM UTCresolved

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

5. March 6, 2026 at 3:38 PM 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. March 4, 2026 at 6:49 PM 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. February 18, 2026 at 6:15 PM 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. February 18, 2026 at 6:32 PM UTCidentified

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

3. February 18, 2026 at 6:49 PM UTCmonitoring

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

4. February 18, 2026 at 7:05 PM UTCresolved

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

5. February 19, 2026 at 6:23 PM 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. January 6, 2026 at 9:40 PM 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. January 8, 2026 at 8:09 PM 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. December 22, 2025 at 5:12 PM 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. December 5, 2025 at 3:47 PM 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. November 18, 2025 at 12:32 PM 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. November 18, 2025 at 12:47 PM UTCinvestigating

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

3. November 18, 2025 at 1:12 PM 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. November 18, 2025 at 1:15 PM UTCmonitoring

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

5. November 18, 2025 at 1:18 PM UTCmonitoring

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

6. November 18, 2025 at 1:56 PM 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. October 29, 2025 at 6:24 PM 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. October 29, 2025 at 6:32 PM UTCidentified

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

3. October 29, 2025 at 6:35 PM UTCmonitoring

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

4. October 29, 2025 at 6:47 PM 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. November 5, 2025 at 2:18 PM 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. October 27, 2025 at 5:49 PM UTCidentified

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

2. October 27, 2025 at 5:52 PM UTCmonitoring

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

3. October 27, 2025 at 5:57 PM 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. October 28, 2025 at 7:40 PM 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. October 16, 2025 at 4:33 PM 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. October 16, 2025 at 6:13 PM 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. October 16, 2025 at 7:17 PM UTCmonitoring

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

4. October 16, 2025 at 7:45 PM UTCresolved

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

5. October 17, 2025 at 2:10 PM 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. October 15, 2025 at 4:41 PM UTCinvestigating

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

2. October 15, 2025 at 4:46 PM UTCidentified

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

3. October 15, 2025 at 4:51 PM UTCmonitoring

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

4. October 15, 2025 at 4:57 PM UTCresolved

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

5. October 16, 2025 at 7:03 PM 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.