Histórico de interrupções do Channable

1. 2 Here 2026 da 08:32 UTCinvestigating

   Identificou-se um problema que causa instabilidade ao tentar usar a ferramenta e causar atrasos no processamento de antecedentes. Estamos a investigar a causa exacta.

2. 2 Here 2026 da 10:08 UTCinvestigating

   Continuamos a investigar esta questão.

3. 2 Here 2026 da 10:45 UTCinvestigating

   A instabilidade aumentou, e a maioria da ferramenta Channable está atualmente indisponível. O processamento de antecedentes, incluindo as importações e as actualizações de alimentos para animais, está ainda mais atrasado. Seus feeds existentes ainda estão disponíveis para seus canais, mas eles não incluirão alterações recentes até que o processamento alcance. Continuamos a trabalhar numa solução.

4. 2 Here 2026 da 13:26 UTCmonitoring

   Aplicámos várias correcções à nossa infra-estrutura. A ferramenta Channable está estável novamente, e o processamento de fundo está de volta à velocidade normal. Insights & Analytics e CSS ainda estão trabalhando através de um backlog, então os dados nessas áreas podem ser atrasados por um tempo mais. Estamos monitorando a situação e vamos postar uma atualização assim que o backlog estiver limpo.

5. 5 Here 2026 da 13:37 UTCmonitoring

   O processamento de fundo para Insights e CSS ainda está vendo atrasos. Se o seu projeto usar essas funcionalidades, o resto da execução do projeto também poderá ser atrasado. Estamos atualmente trabalhando em uma solução para mitigar esses atrasos, e esperamos que isso aconteça amanhã (5 de outubro).

6. 6 Here 2026 da 10:47 UTCmonitoring

   A ferramenta Channable está estável novamente. Aumentamos a capacidade de processamento, e o backlog para Insights, Analytics e CSS foi liberado. Continuaremos a monitorizar nas próximas horas para garantir que continua assim.

7. 6 Here 2026 da 13:54 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Eost 2026 da 11:53 UTCinvestigating

   Estamos actualmente a investigar esta questão.

2. 22 Eost 2026 da 11:57 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 22 Eost 2026 da 12:04 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 22 Eost 2026 da 13:36 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 13:33 UTCinvestigating

   Estamos atualmente tendo uma taxa de erro elevada para produtos e submissões de ofertas através da nossa integração com o Kaufland. Estamos a investigar activamente a questão e estamos em contacto directo com a equipa Kaufland para encontrar uma resolução. Nota: O processamento de pedidos permanece totalmente inalterado. Forneceremos outra atualização assim que tivermos mais informações.

2. 27 Gouere 2026 da 09:27 UTCmonitoring

   Identificamos a causa dos erros e introduzimos alterações para mitigar a questão. As taxas de erro ainda estão elevadas enquanto validamos a eficácia dessas mudanças com Kaufland. Entretanto, o desempenho permanecerá degradado. Continuamos a acompanhar de perto a situação.

3. 29 Gouere 2026 da 13:38 UTCresolved

   Identificámos a causa dos erros e a situação melhorou significativamente. O impacto global é actualmente limitado; no entanto, uma vez que continuamos a ver erros ocasionais, os nossos esforços de atenuação permanecerão em vigor enquanto continuarmos a acompanhar a situação. Se você ainda estiver enfrentando problemas, por favor, contate nossa equipe de suporte para que possamos ajudá-lo ainda mais.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 16:44 UTCmonitoring

   Since 12:00 PM UTC today we have been experiencing a disruption with our Mirakl order connections. This is causing a delay in fetching orders from marketplaces into Channable. We are actively monitorring the issue and will provide an update as soon as we have more information.

2. 1 Gouere 2026 da 11:06 UTCresolved

   All Mirakl orders now being retrieved and processed.

1. 3 Mezheven 2026 da 13:34 UTCinvestigating

   We are experiencing issues with Shopify imports and order processing. Shopify has acknowledged an incident on their end: https://www.shopifystatus.com/ We are investigating what the exact impact of this incident is on our integration and will update once we know more.

2. 3 Mezheven 2026 da 13:57 UTCidentified

   The issues we are seeing are related to the Shopify incident linked below. Shopify imports will not succeed and order synchronization can not succeed while this is ongoing. Notice: You may receive automated emails about failed orders or import updates from Channable features that rely on Shopify. No action is required on your side at this time. These notifications are a side effect of the incident.

3. 3 Mezheven 2026 da 15:01 UTCmonitoring

   Shopify has identified the issue and rolled out a mitigation. We are seeing recovery of order synchronization and processing of import jobs. We will keep monitoring until full recovery of processes.

4. 3 Mezheven 2026 da 15:20 UTCresolved

   The issue has improved and Shopify order sync and stock updates are largely processing again. No action required: Any orders that failed during the incident have been or are being automatically re-sent by us.

1. 22 Mae 2026 da 18:31 UTCinvestigating

   We are investigating a potential issue with Shopify authentication. Channable projects affected by this issue will show a red 'failed' marker for Shopify imports, and will not receive new orders, returns or stock updates. This incident will be updated once we know more.

2. 22 Mae 2026 da 19:04 UTCidentified

   The issue has been identified and a potential fix is being worked on. The potential fix will require manual action from an authorized Shopify user to re-link Channable to Shopify. Instructions to perform this re-linking will be shared once they are ready.

3. 22 Mae 2026 da 19:16 UTCidentified

   We have applied a fix which has allowed stock updates to work again. This means that Channable is again able to notify marketplaces of stock changes when orders are placed on Shopify, but we are not yet able to send new orders or returns from other marketplaces to Shopify.

4. 22 Mae 2026 da 20:19 UTCidentified

   We have identified a fix for the issue affecting Shopify connections. This fix requires manual intervention by an authorized Shopify user, which means Channable cannot apply this fix for you. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection

5. 22 Mae 2026 da 21:11 UTCidentified

   Contrary to our previous update we have identified that stock updates are still affected by this issue. The previously-shared fix for order connections will also fix stock updates and imports from Shopify. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection After renewing the connection any orders that failed while the connection was not working, will need to be re-sent by following the steps in this helpcenter article: https://helpcenter.channable.com/list-advertise/orders/troubleshooting-orders/how-to-fix-resend-a-failed-order#resend-all-orders

6. 23 Mae 2026 da 11:11 UTCidentified

   As part of Shopify's own security measures our Shopify app has been delisted. We are currently reaching out to Shopify to re-list our app as soon as possible. Until that time renewing connections as described in the previous updates is not possible. We will update when it is again possible to renew connection(s) and resend all failed orders.

7. 23 Mae 2026 da 13:18 UTCidentified

   We have identified a fix for renewing Shopify connections while our app remains delisted. We are currently working on implementing this and getting it in our tool. We expect to provide an update on this within 30 minutes.

8. 23 Mae 2026 da 13:33 UTCidentified

   Shopify connections can be renewed again in Channable. Companies with broken Shopify connections will see a notification on log in. To restore Shopify connectivity, please 'Renew' the connection as described in this page: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection. After pressing 'Renew' and logging in to Shopify you will need to press 'Open app'. This triggers the reauthentication process between Channable and your Shopify store.

9. 26 Mae 2026 da 10:34 UTCmonitoring

   Additional instructions for renewing Shopify connections and manual fallback We have provided further details and a manual workaround for users experiencing difficulties renewing their Shopify connection. You can find these full instructions at: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection. - Do NOT uninstall the current Channable app in Shopify during this recovery process. - If the 'Renew' button does not work, you can manually trigger the reauthentication flow by logging into admin.shopify.com, navigating to Installed apps, opening the Channable app, and clicking Open app. - Orders that failed while the connection was down will not automatically retry. Re-send them manually once your connection is active. Note that re-sent orders may take some time to appear in Shopify. If you are still unable to renew your connection after trying the manual fallback, please contact our support team at [email protected].

10. 27 Mae 2026 da 13:53 UTCmonitoring

    The Channable App is still unlisted in Shopify We are aware that the Channable app is no longer listed in Shopify’s app marketplace. We are working with Shopify to get the Channable app re-instated. In the meantime, DO NOT uninstall the Channable app in Shopify. Removing the app will prevent you from renewing your Shopify connection. Follow the renewal instructions here: https://helpcenter.channable.com/get-started/getting-started/connections-in-channable/how-to-renew-a-connection

11. 28 Mae 2026 da 09:49 UTCmonitoring

    Fix implemented for Shopify metafields error message We have released a fix for users encountering the error message "Channable cannot access your Shopify metafields" for their Shopify imports. You can resolve this either by switching to Shopify Markets (if you haven't already done so), OR by applying a workaround in your Channable import settings. We have published the instructions for both methods in our changelog: https://helpcenter.channable.com/changelog#error-message-channable-cannot-access-your-shopify-metafields

12. 28 Mae 2026 da 14:35 UTCmonitoring

    Re-installations and new Shopify connections are now possible While we continue to work with Shopify to get the Channable app re-listed in Shopify's App store, we have identified temporary workarounds as follows: If you uninstalled the Channable app: You can now reinstall it directly from your Shopify admin backend without needing the app marketplace. Follow the instructions here: https://helpcenter.channable.com/changelog#i-uninstalled-the-channable-app-from-shopify If you need to install Channable for the first time: We have identified a direct installation URL that allows you to bypass the marketplace and establish a new connection. Follow the instructions here: https://helpcenter.channable.com/import-data/import-how-to/import-your-product-data/import-via-a-webshop/shopify#install-the-channable-app-in-shopify In addition, all issues affecting order synchronization have been resolved as connection renewal allows processing of all your orders

13. 2 Mezheven 2026 da 14:02 UTCresolved

    We're closing this status page now, as the majority of technical issues have been resolved. We're still working with Shopify to get the Channable app up and running again on the Shopify App store. All workarounds, such as the temporary fix for metafields, still apply. You can stay up-to-date by following the changelog.

1. 12 Mae 2026 da 08:44 UTCinvestigating

   We have identified an issue with background processing that started around 2:15 EST. We are investigating the cause.

2. 12 Mae 2026 da 08:49 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 Mae 2026 da 09:04 UTCidentified

   We have identified the cause and are working on mitigating the issue. Until the this mitigation is in place background jobs will continue processing with delays.

4. 12 Mae 2026 da 09:32 UTCmonitoring

   We have implemented a mitigation and are working through our backlog of background jobs. Imports, Channel exports and other jobs are being processed.

5. 12 Mae 2026 da 10:41 UTCresolved

   This issue has been resolved. We are working through our backlog of background jobs at a normal pace again.

1. 4 Meurzh 2026 da 13:56 UTCidentified

   We have identified an issue which is causing some import jobs to fail to run. Affected jobs will show a red 'Failed' marker in the Channable tool. We have identified a likely cause of the issue and are working on a fix. Any affected import or export jobs will be rerun automatically once we have determined the issue is fixed.

2. 4 Meurzh 2026 da 14:30 UTCmonitoring

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

3. 4 Meurzh 2026 da 14:53 UTCmonitoring

   The issue that was causing the import jobs has been determined to be fixed. We have been made aware of an additional issue which is preventing projects using the image editor from working correctly. Affected projects will also show a red 'Failed' marker in the Channable tool. We have identified the cause of this issue as well and are working on deploying a fix. Any affected export jobs will be rerun automatically once we have determined the issue is fixed.

4. 4 Meurzh 2026 da 15:25 UTCmonitoring

   The issue affecting the exports using the image editor has been confirmed to be fixed. All affected import and export jobs have been resubmitted and will be retried by our system shortly.

5. 4 Meurzh 2026 da 16:26 UTCresolved

   This incident has been resolved.

1. 20 Cʼhwevrer 2026 da 15:22 UTCinvestigating

   Issues loading and processing items causing the tool to sometimes not show pages correctly. We are investigating the scope of the problem at the moment. We can see that exports, rules and creatives are mainly affected.

2. 20 Cʼhwevrer 2026 da 15:30 UTCmonitoring

   Restarted affected services and we will monitor. Missed orders or offer updates will be picked up, although with a slight delay. Any delayed exports or imports will continue to run again.

3. 20 Cʼhwevrer 2026 da 16:31 UTCresolved

   The incident has been resolved. No systems are currently affected anymore and processes are being caught up on. Do note that there still might be a small delay while we work through the backlog of tasks that got delayed.

1. 23 Genver 2026 da 11:46 UTCmonitoring

   Since January 20th, we have observed a reduction in performance for our Shopify order connections, occasionally resulting in the error message 'Unable to claim inventory' during order creation. Shopify is aware of this issue and is actively working on a solution. We have implemented measures to addressing this issue by increasing retries on order creation, to mitigate the impact. For any failed orders, the current workaround is to manually resend the Shopify order within our platform. We are monitoring the situation closely and will provide updates on this page as the situation evolves. Please note: This incident is isolated and does not affect any of our other integrations.

2. 26 Genver 2026 da 13:13 UTCresolved

   This incident has been resolved. After an extended period of monitoring, we have confirmed that Shopify orders are once again being created successfully and error rates have returned to normal. All systems are fully operational. Thank you for your patience.

1. 19 Genver 2026 da 08:07 UTCidentified

   Our phone provider is experiencing issues with their authentication system. This means our support department is not reachable by telephone. We are still reachable through all other means

2. 19 Genver 2026 da 08:45 UTCidentified

   We are continuing to work on a fix for this issue.

3. 19 Genver 2026 da 08:45 UTCresolved

   This incident has been resolved.

1. 3 Kerzu 2025 da 08:37 UTCinvestigating

   We are currently investigating a report about Returns not working as expected for different Mirakl platforms (i.e. Carrefour, Fonq and Kruidvat among others). We are determining the impact as we speak. Exports to these channels or regular Order handling remain unaffected.

2. 3 Kerzu 2025 da 08:54 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 Kerzu 2025 da 10:05 UTCresolved

   We have determined what caused the problem and changed our internal logic for handling Returns for the different Mirakl platforms. The system is now quicker and more robust. Handling of returns will continue and works as expected. Other features were fully unaffected.

1. 18 Du 2025 da 12:43 UTCidentified

   We have identified that we are affected by an ongoing outage in the global Cloudflare network. While this incident is ongoing images using background removal or the image editor may not work and fail to load with a 500 server error. This means that platforms configured to load feeds with images processed through Channable will not be able to load them. Exported feeds themselves are unaffected at this time and are being updated normally. Cloudflare is providing updates for this outage at the following URL: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. 18 Du 2025 da 15:03 UTCmonitoring

   Cloudflare has reported that a fix has been implemented for the outage, and we can confirm that the performance of the affected infrastructure has significantly improved. We are still monitoring the situation to conclude whether the effect on Channable's infrastructure has fully been resolved.

3. 18 Du 2025 da 18:12 UTCresolved

   This incident has been resolved.

1. 7 Du 2025 da 08:51 UTCinvestigating

   We are currently investigating a problem with our rule processing engine which leads to degraded performance of item processing in Channable. This means that any page where items are shown in Channable will not work as expected and might show signs of slowness.

2. 7 Du 2025 da 08:58 UTCinvestigating

   After some further complications, Channable is reported to be unreachable for certain users. We are working to add processing capacity in order to restore operations.

3. 7 Du 2025 da 09:03 UTCmonitoring

   The issue was identified and our expected solution is having a positive effect on the recovery of the system. We are actively monitoring while the system recovers.

4. 7 Du 2025 da 10:17 UTCresolved

   After monitoring we concluded that our systems are operational again and back to their original state of working.

1. 9 Here 2025 da 06:33 UTCinvestigating

   We are currently investigating this issue.

2. 9 Here 2025 da 07:04 UTCmonitoring

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

3. 9 Here 2025 da 10:07 UTCresolved

   This incident has been resolved.

1. 26 Eost 2025 da 06:46 UTCinvestigating

   We are currently investigating this issue.

2. 26 Eost 2025 da 07:15 UTCinvestigating

   We are seeing an high backlog of failed imports that originate from the 'docs.google.com' domain. Because of this, other systems got backed up too. We are actively working on unclogging the backlog and getting systems operational again. The systems surrounding orders are unaffected.

3. 26 Eost 2025 da 07:19 UTCinvestigating

   While we work to resolve the blockade, we were forced to pause our jobs system. So no importers or exporters are running at the moment, everything remains queued for now.

4. 26 Eost 2025 da 08:24 UTCidentified

   The jobs system is unpaused. All projects not in scope of the problem are unblocked and are running again. All projects relying on a Google Spreadsheet importer are still being blocked.

5. 26 Eost 2025 da 14:22 UTCmonitoring

   Google is rolling out a fix, projects relying on the Google Spreadsheet importer are no longer blocked. We will continue to monitor the status.

6. 27 Eost 2025 da 07:56 UTCresolved

   After monitoring for a while we concluded that the problems have been resolved and systems are back to normal operation.

1. 14 Eost 2025 da 16:19 UTCmonitoring

   The image downloader is experiencing heavy load. We have applied performance improvements but it will take more time for us to fully catch up with the backlog. In the meantime, this might temporarily cause a `NOT DOWNLOADED YET` error to be shown for new images that we have not downloaded before.

2. 15 Eost 2025 da 09:11 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 16 Eost 2025 da 08:32 UTCresolved

   This incident has been resolved.

1. 13 Eost 2025 da 14:26 UTCidentified

   We are seeing an increase in failed exports because part of the creatives suite is not working as expected. We are actively working to resolve this problem, however for certain exports that use the Image Editor it could result in failures. The hosted feeds are unaffected, but won't be updated when this problem happens. Other parts of the tool, including the downloading of images, are not affected.

2. 13 Eost 2025 da 14:56 UTCmonitoring

   For a small number of projects, a small number of product image files have been causing problems. A temporary fix has been implemented, causing us to mark images that are affected by the problem to appear as `NOT AVAILABLE`. The items causing problems can be omitted by editing your Image Generation Safety settings in the feed, or you can choose to wait for the problem to be fully resolved.

3. 20 Eost 2025 da 13:54 UTCresolved

   This incident has been resolved.

1. 7 Eost 2025 da 13:39 UTCidentified

   We are seeing delays in fetching images for our creatives suite. New images may be delayed by several hours. Images that have already been downloaded into our systems will function as normal. The problem has been identified and we are working on a solution.

2. 7 Eost 2025 da 15:05 UTCmonitoring

   A fix has been deployed and we are making progress towards our backlog. We expect to have caught up in a few more hours.

3. 8 Eost 2025 da 11:40 UTCresolved

   Our backlog has been cleared and everything is operational.

1. 25 Mezheven 2025 da 10:33 UTCidentified

   We have identified an issue with Beslist stock updates. We have paused them for now and new updates will not be visible in the app. We will unpause them as soon as things are running smoothly again.

2. 26 Mezheven 2025 da 10:00 UTCmonitoring

   Beslist stock updates are being processed again, we will continue to monitor the situation.

3. 26 Mezheven 2025 da 11:29 UTCresolved

   This incident has been resolved.