Channable 中断历史

1. 2026年10月2日 UTC 08:32investigating

   我们查明了一个在试图使用该工具时造成不稳定并造成背景处理延误的问题。 我们正在调查确切的原因.

2. 2026年10月2日 UTC 10:08investigating

   我们正在继续调查这一问题.

3. 2026年10月2日 UTC 10:45investigating

   不稳定性已经增加,目前大部分Channable工具无法使用. 背景处理,包括进口和饲料更新,进一步被拖延. 您已有的种子仍然可供您的频道使用, 但它们不会包括最近的更改, 直到处理赶上为止 。 我们正在继续研究一个解决方案.

4. 2026年10月2日 UTC 13:26monitoring

   我们已对我们的基础设施进行了若干修正。 Channable工具再次稳定,背景处理恢复到正常速度. 透视分析(Insights & Analytics)和CSS(CSS)仍在工作,因此这些领域的数据可能会被推迟一段时间. 我们正在监测局势,一旦积压工作得到清理,我们将公布最新情况.

5. 2026年10月5日 UTC 13:37monitoring

   Insights和CSS的背景处理仍然出现延误. 如果您的项目使用这些功能,项目的其他运行也可能被推迟. 我们目前正在想方设法减轻这些拖延,并期望在明天(10月5日)之前推出.

6. 2026年10月6日 UTC 10:47monitoring

   Channable工具再次稳定. 我们已经提高了处理能力,Insights、Analytics和CSS的积压已经清理完毕。 我们将继续在今后几个小时进行监测,以确保它保持这种状态.

7. 2026年10月6日 UTC 13:54resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月22日 UTC 11:53investigating

   我们目前正在调查这一问题.

2. 2026年8月22日 UTC 11:57identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年8月22日 UTC 12:04monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年8月22日 UTC 13:36resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月24日 UTC 13:33investigating

   目前,我们的产品误差率上升,并通过我们的考夫兰一体化提交材料。 我们正在积极调查这一问题,并与考夫兰小组直接接触以寻求解决办法。 注:订单处理不受影响。 一旦掌握更多信息,我们将提供另一个最新情况.

2. 2026年7月27日 UTC 09:27monitoring

   我们已查明出错的原因,并进行了修改,以缓解这一问题。 目前,在我们与考夫兰核实这些变化的有效性时,错误率仍在上升。 在此期间,业绩将继续下降。 我们正在继续密切监测局势.

3. 2026年7月29日 UTC 13:38resolved

   我们已查明出错的原因,情况已大有改观。 总体影响目前有限;然而,由于我们仍然偶尔看到出错,我们的缓解努力将继续进行,同时继续监测局势。 如果你还遇到问题,请联系我们的支援小组,以便我们进一步协助你.

自动翻译自官方事件更新。

1. 2026年6月30日 UTC 16:44monitoring

   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. 2026年7月1日 UTC 11:06resolved

   All Mirakl orders now being retrieved and processed.

1. 2026年6月3日 UTC 13:34investigating

   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. 2026年6月3日 UTC 13:57identified

   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. 2026年6月3日 UTC 15:01monitoring

   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. 2026年6月3日 UTC 15:20resolved

   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. 2026年5月22日 UTC 18:31investigating

   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. 2026年5月22日 UTC 19:04identified

   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. 2026年5月22日 UTC 19:16identified

   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. 2026年5月22日 UTC 20:19identified

   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. 2026年5月22日 UTC 21:11identified

   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. 2026年5月23日 UTC 11:11identified

   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. 2026年5月23日 UTC 13:18identified

   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. 2026年5月23日 UTC 13:33identified

   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. 2026年5月26日 UTC 10:34monitoring

   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. 2026年5月27日 UTC 13:53monitoring

    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. 2026年5月28日 UTC 09:49monitoring

    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. 2026年5月28日 UTC 14:35monitoring

    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. 2026年6月2日 UTC 14:02resolved

    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. 2026年5月12日 UTC 08:44investigating

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

2. 2026年5月12日 UTC 08:49investigating

   We are continuing to investigate this issue.

3. 2026年5月12日 UTC 09:04identified

   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. 2026年5月12日 UTC 09:32monitoring

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

5. 2026年5月12日 UTC 10:41resolved

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

1. 2026年3月4日 UTC 13:56identified

   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. 2026年3月4日 UTC 14:30monitoring

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

3. 2026年3月4日 UTC 14:53monitoring

   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. 2026年3月4日 UTC 15:25monitoring

   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. 2026年3月4日 UTC 16:26resolved

   This incident has been resolved.

1. 2026年2月20日 UTC 15:22investigating

   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. 2026年2月20日 UTC 15:30monitoring

   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. 2026年2月20日 UTC 16:31resolved

   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. 2026年1月23日 UTC 11:46monitoring

   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. 2026年1月26日 UTC 13:13resolved

   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. 2026年1月19日 UTC 08:07identified

   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. 2026年1月19日 UTC 08:45identified

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

3. 2026年1月19日 UTC 08:45resolved

   This incident has been resolved.

1. 2025年12月3日 UTC 08:37investigating

   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. 2025年12月3日 UTC 08:54investigating

   We are continuing to investigate this issue.

3. 2025年12月3日 UTC 10:05resolved

   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. 2025年11月18日 UTC 12:43identified

   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. 2025年11月18日 UTC 15:03monitoring

   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. 2025年11月18日 UTC 18:12resolved

   This incident has been resolved.

1. 2025年11月7日 UTC 08:51investigating

   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. 2025年11月7日 UTC 08:58investigating

   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. 2025年11月7日 UTC 09:03monitoring

   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. 2025年11月7日 UTC 10:17resolved

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

1. 2025年10月9日 UTC 06:33investigating

   We are currently investigating this issue.

2. 2025年10月9日 UTC 07:04monitoring

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

3. 2025年10月9日 UTC 10:07resolved

   This incident has been resolved.

1. 2025年8月26日 UTC 06:46investigating

   We are currently investigating this issue.

2. 2025年8月26日 UTC 07:15investigating

   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. 2025年8月26日 UTC 07:19investigating

   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. 2025年8月26日 UTC 08:24identified

   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. 2025年8月26日 UTC 14:22monitoring

   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. 2025年8月27日 UTC 07:56resolved

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

1. 2025年8月14日 UTC 16:19monitoring

   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. 2025年8月15日 UTC 09:11monitoring

   We are continuing to monitor for any further issues.

3. 2025年8月16日 UTC 08:32resolved

   This incident has been resolved.

1. 2025年8月13日 UTC 14:26identified

   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. 2025年8月13日 UTC 14:56monitoring

   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. 2025年8月20日 UTC 13:54resolved

   This incident has been resolved.

1. 2025年8月7日 UTC 13:39identified

   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. 2025年8月7日 UTC 15:05monitoring

   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. 2025年8月8日 UTC 11:40resolved

   Our backlog has been cleared and everything is operational.

1. 2025年6月25日 UTC 10:33identified

   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. 2025年6月26日 UTC 10:00monitoring

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

3. 2025年6月26日 UTC 11:29resolved

   This incident has been resolved.