aug 3 ， 12:00 UTC
<强>解决 - 我们已经解决了这一事件。
Aug 3, 08:00 UTC
Update - We are seeing the connector failure count reduce significantly while we still wait for an update from Twitter's team.
Aug 2, 13:37 UTC
Update - We are continuing to see failures due to delayed response times from Twitter's API. This has been reported on the Twitter Community and we have filed this an issue as well - https://twittercommunity.com/t/async-analytics-takes-forever-to-complete-for-the-past-few-days-and-today/157478/2?u=fivetrand
We are currently waiting for Twitter to acknowledge this issue and work with them towards a resolution.
Aug 2, 06:57 UTC
Monitoring - This is transient on Twitter’s end and we’re starting to see a few connectors sync successfully. We'll continue to monitor the syncs.
Aug 1, 18:48 UTC
Identified - The issue has been identified and we are working to resolve it.
jul 31 ， 01:21 UTC
<强>解决 - 我们已经解决了这一事件。
Jul 30, 22:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 30, 18:51 UTC
Update - DV360 connectors are failing with the HTTP 303 error caused by an incident on the Google side. Some of the metrics and dimensions became unavailable for the specific users. We are requesting assistance from our customers to contact DV360 Support via the link below in order to gain traction towards a quicker resolution.
https://support.google.com/displayvideo/contact/nghelp_contact_form
Jul 30, 18:48 UTC
Identified - The issue has been identified and we are working to resolve it.
Jul 28， 18:15 UTC
Resolved -我们已经解决了这个问题。
Jul 28， 15:18 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 28， 08:39 UTC
Identified -问题已经被识别出来，我们正在解决它
Jul 27， 06:30 UTC
Resolved -连接器开始失败，一个“空指针异常”，然后是“原因:无法通过区域提供者链找到一个区域”。必须在构建器或设置环境中提供一个显式区域来提供一个区域。
问题已被识别并部署了修复
Jul 0 ， 12:10 UTC
Resolved -我们已经解决了这个问题。
Jul 20， 10:40 UTC
Update -我们注意到许多连接器处于挂起状态，并识别出内部更改的原因。我们已经恢复了这个更改并重新启动了服务器。您可能会注意到连接器已经重新启动。
Jul 20， 10:10 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 20， 10:10 UTC
Identified -问题已经被识别出来，我们正在解决它
jul 16 ， 03:40 UTC
<强>解决 - 我们已经解决了这一事件。
Jul 16, 03:40 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 15, 23:00 UTC
Identified - The issue has been identified and we are working to resolve it.
jul 14 ， 10:44 UTC jul 14 ，10:30 UTC jul jul 14 ， 10:16 utc
<强>解决 - 此事件已得到解决。
根本原因确定，我们正在努力解决它。
jul 13 ， 07:26 UTC jul 12 ，14:01 UTC jul jul 9 ， 14:17 UTC jul 6 ， 10:35 Utc jul 5 ， 16:00 utc jul 5 ， 15:58 UTC
<强>解决 - 事件已得到解决。
监控 - 已经实施了修复程序，我们正在监控结果。
更新 - 我们正在继续解决这个问题的修复。
更新 - 我们目前正在测试此问题的修复程序。目前的部署ETA是7月12日。在美国地区的此时间内，一些转换可能仍然受到延迟的影响。
更新 - 我们正在继续进行此问题的修复程序。在此期间，一些转换可能会间歇性地影响。
标识 - 已识别出问题，我们正在努力解决它。
jul 9 ， 20:30 UTC jul 9 ，20:11 UTC 标识 - 已识别出问题并正在实施修复程序。 jul
<强>解决 - 此事件已得到解决。
Jul 3， 05:20 UTC
Resolved -我们已经解决了这个问题。
Jul 3， 00:20 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 2， 16:40 UTC
Identified -问题已经被识别出来，我们正在解决它
jul 2 ， 17：00 UTC jul 2 ， jul 2 ， 07:40 UTC
<强>解决 - 我们已经解决了这一事件。已经准备了一个电子邮件通信，使用步骤来解决连接器问题，并且将很快发送。
标识 - 已经确定了问题，我们正在努力解决它。Criteo连接器必须升级到Criteo API的v2，因为v1已弃用。
Jul 1， 09:30 UTC
Resolved -我们已经解决了这个问题。
Jul 1， 05:12 UTC
Monitoring -问题已经解决，表重新同步通过仪表盘触发，现在正常工作。
Jun 30， 22:10 UTC
Identified -问题已经被识别出来，我们正在解决它
jun 30 ， 21:40 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 30, 18:32 UTC
Monitoring - A fix has been implemented from the Google DV360 side and connectors have started syncing successfully. We are monitoring the syncs now.
Jun 30, 00:04 UTC
Update - Connectors are failing with the HTTP 303 error possibly caused by changes on the Google side. Some of the metrics and dimensions became unavailable for the specific users. We are requesting assistance from our customers to contact DV360 Support via the link below in order to gain traction towards a quicker resolution.
https://support.google.com/displayvideo/contact/nghelp_contact_form
Jun 29, 21:40 UTC
Identified - The issue has been identified and we are working to resolve it.
jun 29 ， 04:30 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 29, 01:40 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 28, 17:20 UTC
Identified - The issue has been identified and we are working to resolve it.
jun 28 ， 17:50 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 28, 17:50 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 28, 15:40 UTC
Identified - The issue has been identified and we are working to resolve it.
jun 28 ， 03：45 UTC jun 28 ， 00:41 UTC
<强>解决 - 杠杆表明他们已经解决了这个问题。同步再次成功递增。
Jun 22， 16:30 UTC
Resolved -我们已经解决了这个问题。
Jun 22， 13:30 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jun 22， 10:36 UTC
Identified - PostgreSQL和Facebook连接器设置测试失败的错误"测试计数不匹配"和"连接测试失败"
jun 21 ， 23:10 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 21, 23:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 21, 20:00 UTC
Identified - The issue has been identified and we are working to resolve it.
Jun 17， 15:50 UTC
Resolved -我们已经解决了这个问题。
Jun 17， 15:09 UTC
Monitoring -我们已经发布了一个修复，如果有任何返回错误，可以暂时跳过“overpayment”表的同步。
下一步:
我们正在等待Xero支持对解决这个问题的根本原因的答复。根据该决议，我们将删除临时表跳过。
Jun 17， 13:09 UTC
Update -一些连接器失败，错误包含"Primary Key overpaymentID is null in object"。
这是由Xero API错误地将OverpaymentId值返回为null引起的。Xero文档告诉我们这个值应该是唯一的:
https://developer.xero.com/documentation/api/accounting/overpayments#get-overpayments。
我们看到一些客户自己解决了这个问题，我们正在联系Xero支持来解决这个问题。
Jun 17， 08:00 UTC
Identified -问题已经被识别出来，我们正在解决它
jun 17 ， 04:30 UTC
<强>解决了 - MixPanel连接器由于在其状态页面上观察到MixPanel的出口API部分中断 - https://status.mixpanel.com/
jun 15 ， 06:13 UTC jun 15 ，03:53 UTC jun 15 ， 03：20 UTC jun 15 ， 03：00 UTC
<强>解决 - 此事件已得到解决。
更新 - 我们继续监控任何进一步的问题。
监控 - 修复已实现我们正在监控结果。
标识 - 已识别出问题，我们正在努力解决它。
jun 12 ， 13:10 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 12, 10:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 12, 02:50 UTC
Identified - Syncs are running as expected, but UI elements including sync charts, user actions, schema changes may not be visible for some users
jun 9 ， 10:20 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 9, 07:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 15:48 UTC
Update - The issue identified is confirmed to be on the Facebook side. Fivetran Engineering has reached out to Facebook Support and are awaiting an ETA for resolution. You can find additional details here: https://developers.facebook.com/support/bugs/200868658566193/
We are requesting your help to update the above Facebook bug in order to gain traction towards a quicker resolution.
Jun 8, 02:50 UTC
Identified - The issue has been identified and we are working to resolve it.
jun 4 ， 21:10 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 4, 21:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 4, 17:00 UTC
Identified - The issue has been identified and we are working to resolve it.
may 30 ， 20:40 UTC
May 30, 20:40 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 30, 19:11 UTC
Update - These are the two errors seen from the connector perspective:
- An unknown error occurred
- Please reduce the amount of data you’re asking for, then retry your request
May 30, 18:51 UTC
Update - The root cause of this appears to a performance issue with the Facebook API.
You can track Facebook's progress in correcting the root cause here:
https://developers.facebook.com/status/issues/441591440472829/
Our developers are looking for workarounds in the meantime to mitigate the failures seen in our connectors.
May 30, 18:50 UTC
Identified - The issue has been identified and we are working to resolve it.