aug 7 ， 14:54 UTC
<强>解决 - 我们已经解决了这一事件。
Aug 7, 13:51 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 6, 23:09 UTC
Identified - The issue has been identified and we are working to resolve it.
<小>八月
Aug 7, 06:48 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 6, 22:57 UTC
Identified - The issue has been identified and we are working to resolve it.
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, 15:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 28, 08:39 UTC
Identified - The issue has been identified and we are working to resolve it.
jul 27 ， 06:30 UTC
<强>解决 - 连接器开始使用“null指针例外”后跟“原因：无法通过区域提供程序链查找一个区域。必须在构建器或设置环境中提供显式区域以提供一个区域。”。
已识别出问题并部署了一个修复程序
jul 20 ， 12:10 UTC
<强>解决 - 我们已经解决了这一事件。
Jul 20, 10:40 UTC
Update - We noticed that many connectors were in hung state and identified the cause to be an internal change. We have reverted this change and the restarted our server. You may notice your connectors to have restarted.
Jul 20, 10:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 20, 10:10 UTC
Identified - The issue has been identified and we are working to resolve it.
Jul 16， 03:40 UTC
Resolved -我们已经解决了这个问题。
Jul 16， 03:40 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 15， 23:00 UTC
Identified -问题已经被识别出来，我们正在努力解决它
Jul 14， 10:44 UTC
Resolved -此事件已解决。
Jul 14， 10:30 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 14， 10:23 UTC
Update -一些连接器同步可能被延迟，在访问仪表板时也可能有问题。
Jul 14， 10:16 UTC
Identified - Fivetran站点关闭，连接器被延迟。
根本原因已经确定，我们正在努力解决它。
Jul 13， 07:26 UTC
Resolved -事件已经解决。
Jul 12， 14:01 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jul 9， 14:26 UTC
Update -我们正在继续修复这个问题。
Jul 9， 14:17 UTC
Update -我们目前正在测试这个问题的修复。目前预计部署时间是7月12日。在此期间，美国地区的一些转型仍可能受到间歇性延迟的影响。
Jul 6， 10:35 UTC
Update -我们正在继续修复这个问题。在此期间，一些转换可能会间歇性地受到影响。
Jul 5， 16:00 UTC
Identified -问题已经被识别出来，我们正在努力解决它。
Jul 5， 15:58 UTC
Investigating -我们目前正在调查这个问题
jul 9 ， 20:30 UTC jul 9 ，20:11 UTC 标识 - 已识别出问题并正在实施修复程序。 jul
<强>解决 - 此事件已得到解决。
jul 3 ， 05:20 UTC
<强>解决 - 我们已经解决了这一事件。
Jul 3, 00:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 2, 16:40 UTC
Identified - The issue has been identified and we are working to resolve it.
jul 2 ， 17：00 UTC jul 2 ， jul 2 ， 07:40 UTC
<强>解决 - 我们已经解决了这一事件。已经准备了一个电子邮件通信，使用步骤来解决连接器问题，并且将很快发送。
标识 - 已经确定了问题，我们正在努力解决它。Criteo连接器必须升级到Criteo API的v2，因为v1已弃用。
<小>月
Jul 1, 05:12 UTC
Monitoring - The issue has been resolved and the table re-syncs triggered via dashboard, are now working as usual.
Jun 30, 22:10 UTC
Identified - The issue has been identified and we are working to resolve it.
<小>君
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
Resolved -杠杆已经表明他们已经解决了问题。同步再次成功增加。
Jun 28， 00:41 UTC
我们正在调查这个问题
jun 22 ， 16:30 UTC
<强>解决 - 我们已经解决了这一事件。
Jun 22, 13:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 22, 10:36 UTC
Identified - PostgreSQL and Facebook connectors set up tests are failing on the errors "Tests count mismatch." and "Connection tests failed"
<小>君
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
<强>解决 - 我们已经解决了这一事件。
Jun 17, 15:09 UTC
Monitoring - We have released a fix to temporarily skip the sync of the "overpayment" table if there are any errors returned for it.
Next Steps:
We are waiting for Xero support to reply on the resolution of the root cause of this issue. Following the resolution, we will remove the temporary table skip.
Jun 17, 13:09 UTC
Update - Some connectors are failing with an error containing "Primary Key overpaymentID is null in object".
This is caused by the Xero API incorrectly returning the OverpaymentId values as null. The Xero documentation informs that this should be a unique value:
https://developer.xero.com/documentation/api/accounting/overpayments#get-overpayments.
We are seeing this get resolved by itself for some customers and we are in the process of reaching out to Xero Support to resolve this.
Jun 17, 08:00 UTC
Identified - The issue has been identified and we are working to resolve it.
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
Resolved -我们已经解决了这个问题。
Jun 12， 10:10 UTC
Monitoring -修复已经实现，我们正在监控结果。
Jun 12， 02:50 UTC
Identified -同步运行如预期，但UI元素，包括同步图表，用户操作，模式更改可能对某些用户不可见
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.