Viedoc kesinti geçmişi

1. 8 Eylül 2026 14:07 UTCinvestigating

   Viedoc'daki EDC eylemleri tarafından başlatılan e-posta uyarıları, aşağıdaki zaman pencereleri sırasında AB üretim örneğinde kesintiye uğramamıştır: Pazartesi, 31 Ağustos - 17:25 CEST Perşembe, 3 Eylül 13:31 CEST – Cuma, 4 Eylül 22:07 CEST Çoğu e-posta beklendiği gibi gönderilir, ancak bir alt set gecikir veya bazı durumlarda teslim edilmez. Başka hiçbir örnek etkilenmez. Aktif olarak araştırıyoruz ve daha fazla bilgi olarak güncelleştirmeleri yayınlayacağız.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 4 Eylül 2026 16:15 UTCresolved

   Müşterilere yaklaşık 23:00 ve 00:00 arasında .cn portallarına ulaşamadığı geçici bir rahatsızlık vardı. Sorun altyapımızdaydı ve inkonvencience için özür diledik. Sistemler normale geri döndü ve gizlilik veya bütünlüğü ile ilgili bir sorun yok. Bu problem sadece sistemlerimize erişimi etkiledi.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Ağustos 2026 09:54 UTCmonitoring

   Fransa Merkez bölgesinde Azure'dan temel bir platform bileşeninde deneyimliyoruz, bu kısa süreler için mevcut olmayan hizmet olarak deneyimleyebileceğiniz bazı trafik kaybı yaratıyor. Biz araştırıyoruz ve burada yayınlayacaksınız.

2. 17 Ağustos 2026 10:09 UTCmonitoring

   Daha fazla sorun için izlemeye devam ediyoruz.

3. 17 Ağustos 2026 11:25 UTCresolved

   Olay şimdi Microsoft tarafından çözüldü ve Viedoc paketinin tekrar tamamen operasyonel olduğunu doğrulayabiliriz. Bu rahatsızlıktan özür dileriz.

4. 17 Ağustos 2026 12:27 UTCpostmortem

   # # # Özet Azure \ (Azure App hizmetleri\)'den temel bir platform bileşeni içinde deneyimli sorunlar yaşadık, bu da müşterilerin mevcut olmadığı hizmet kaybı yarattı. Sistem izlememiz sorunları hemen yakaladı ve 1 dakika içinde yanıt veren platform ekibimizi uyardı. Problemin Platform sağlayıcısıyla birlikte olduğunu 15 dakika içinde onaylayabiliriz. # # Instances etkilenen Avrupa'daki tüm ürünler # # # 2026-08-17 09:32 UTC to 2026-08-17 11:20 UTC. # # # Root Cause Microsoft Azure Cloud'daki bir altyapı bileşeni, Fransa Merkez Bölgesi'ndeki Azure App Service platformu içindeki adreslerden sorumlu bir şekilde operasyonel eşleri aştı ve müşteri iş yüklerini destekleyen hizmet kaynaklarının varlığını azalttı. Sonuç olarak, Viedoc, geçici erişilebilirlik sorunları yaşadı ve başarısız talepleri başarısız oldu. ## Effects Bu etkilenen Viedoc erişilebilirliği, güvenliğe veya mahremiyeti etkilemeden etkiledi. ## Actions Kapasite konusunda platform sağlayıcı ile takip edin.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 29 Temmuz 2026 13:35 UTCinvestigating

   Şu anda bu konuyu araştırıyoruz, yakında geliyor.

2. 29 Temmuz 2026 14:11 UTCinvestigating

   Sorun Çin'de bir veri merkezi ihmal ile ilişkilendirilir ve araştırmaya devam ediyoruz.

3. 29 Temmuz 2026 17:06 UTCresolved

   Olay Azure Cloud Çin'de bir sorun olarak tespit edildi ve şimdi sorun azaltıldı. Bir kök nedeniyle analizimiz olduğunda, bir olay raporu ile güncelleyeceğiz. Herhangi bir rahatsızlıktan özür dileriz.

4. 31 Temmuz 2026 13:23 UTCpostmortem

   # # # Özet Çin bölgemiz, sistem bileşenlerimiz arasındaki iç mesajlaşma ile ilgili platform sağlayıcımızda bir yapılandırma hatası nedeniyle kesintiye maruz kaldı, ürün paketimizi 4 saat ve 40 dakika boyunca etkin bir şekilde yerine getiremedi. Müşteri etkisi, normalde çok düşük trafik hacmi ile Çin'de bu gece olduğu için düşük olması bekleniyor. Sistem izlememiz sorunları hemen yakaladı ve 1 dakika içinde yanıt veren platform ekibimizi uyardı ve sorunun Platform sağlayıcısıyla birlikte olduğunu 1 saat içinde onaylayabiliriz. Bir tür bir destek bileti, gerçekten 2 saat ve 32 dakika sonra bir sorun olduğunu onaylayan platform sağlayıcımızla giriş yapıldı ve bundan 38 dakika sonra çözüldü. # # Instances etkilenen Çin'deki tüm ürünler # # # 2026-07-29 12:07 UTC to 2026-07-29 16:47 UTC. # # # Root Cause Çin'deki platform sağlayıcımız tarafından bir yapılandırma hatası, 21ViaNet/Microsoft Azure Cloud China. ## Effects Sadece erişilebilirlik. Veri bütünlüğü ve veri gizliliği etkilenmedi. ## Actions İşletim prosedürlerini, izleme ve olay yanıtlarını geliştirmek üzere platform sağlayıcı ile takip edin.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 9 Temmuz 2026 21:40 UTCidentified

   4.95 sürümünden beri, Viedoc Sitenin yerel zaman bölgesinden ziyade UTC zamanını kullanarak veritabanında teslimatlar kaydedildi. UTC tarihi ve sitenin yerel tarihi teslim zamanında farklıysa, Viedoc Clinic'teki olay tarihi yerel tarih yerine UTC tarihini yanlış yansıtacaktır. Çalışma tasarımında açıklanan veri girişi pencerelerine bağlı olarak, bu aynı zamanda dış-piow sorgularına da neden olabilir. Viedoc Clinic UI'de denetim izi, "Show History" ile erişildi, yerel zamana göre doğru tarihi ve zaman damgasını gösterir. Bu konu hem Viedoc Me uygulamasının mevcut ve mirasını etkiler. Sorun tespit edildi ve bir düzeltme şu anda hazır. Fix, sitenin yerel zaman bölgesini kullanarak yeni gönderimlerin depolanmasını sağlayacaktır, ancak çoktan meydana gelen aşırı sol sorguları veya dışlayıcı sorguları düzeltmeyecektir. Bunlar gelecekteki bir güncellemede ele alınacaktır.

2. 14 Temmuz 2026 14:57 UTCidentified

   Bu sorunu mümkün olduğunca çabuk çözmek için aktif olarak çalışıyoruz. Sıcak bir ek şu anda sonlandırılmış ve test ediliyor ve önümüzdeki haftanın ilk yarısında üretime açık olacağını tahmin ediyoruz.

3. 16 Temmuz 2026 06:53 UTCidentified

   Bugün gün boyunca sıcak eki üretim ortamlarına salıvermeye başlayacağız. Bir güncelleme, her durumda sürüm tamamlandıktan sonra yayınlanacak.

4. 16 Temmuz 2026 09:42 UTCresolved

   Olay, tüm eğitim ve üretim örnekleri için 495.2'nin serbest bırakılmasıyla çözüldü. Bu sürüm, sorunu tekrar edenlerden önletir. Bununla birlikte, UTC'de kaydedilmiş olan olay tarihler artık değişmeden kalacaktır ve bu konu tarafından tetiklenen herhangi bir dışlayıcı sorgu sorguları da düzeltilmesine kadar kalacaktır. Şu anda UTC'de saklanan kehanetler daha sonraki bir tarihte düzeltilecektir. Bu düzeltme için zamanlama henüz doğrulanmadı.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 10 Haziran 2026 18:32 UTCinvestigating

   After the Viedoc 4.95 release, when a revision is applied to a form containing a repeating item group, and a user upgrades the form from the landing page, data previously entered in the repeating item group is cleared. The issue is occurring on the EU and US training and production instances. Investigation is ongoing. Until further information is known, we advise all customers to refrain from applying revisions requiring form upgrades on forms containing repeating item groups.

2. 10 Haziran 2026 23:31 UTCidentified

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

3. 16 Haziran 2026 14:45 UTCidentified

   Hotfix 4.95.1 has been released on the US training and production instances. The incident is resolved on those instances. The hotfix will be deployed to EU training and production instances tomorrow.

4. 17 Haziran 2026 10:40 UTCresolved

   Hotfix 4.95.1 has been released on the EU training and production instances. The incident is now resolved on all instances.

1. 3 Haziran 2026 12:12 UTCmonitoring

   Temporary operational disturbance observed in the Viedoc suite on the Chinese instance (clinic.viedoc.cn).

2. 3 Haziran 2026 13:23 UTCresolved

   This incident has been resolved.

1. 28 Mayıs 2026 07:35 UTCinvestigating

   Operational disturbance observed in Viedoc suite on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing since 05:20 CMT

2. 28 Mayıs 2026 07:38 UTCresolved

   The incident has been resolved since 06:40 CMT

1. 18 Mayıs 2026 10:24 UTCinvestigating

   Operational disturbance observed in Training on the Chinese instance (clinic.viedoc.cn). Investigations are ongoing.

2. 18 Mayıs 2026 10:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 Mayıs 2026 10:32 UTCresolved

   This incident has been resolved.

1. 6 Mayıs 2026 09:48 UTCidentified

   After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. We are working on a fix for these issues.

2. 7 Mayıs 2026 06:34 UTCidentified

   After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. - Intermittent failures in Designer, where users are unexpectedly logged out, are affecting certain users. We are working on a fix for these issues, and the Designer issue is currently under investigation.

3. 8 Mayıs 2026 08:22 UTCidentified

   A hotfix is currently being prepared and will be deployed to both our EU and US instances. Based on preliminary timelines, we expect this release to go out on Monday, May 11.

4. 11 Mayıs 2026 09:54 UTCresolved

   This incident was resolved this morning with the release of hotfix version 4.94.1 on both the EU and US instances.

1. 27 Nisan 2026 13:04 UTCinvestigating

   Operational disturbance observed in Viedoc 4 on the European instance (v4.viedoc.net). Investigations are ongoing.

2. 27 Nisan 2026 17:40 UTCinvestigating

   Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.

3. 27 Nisan 2026 17:42 UTCmonitoring

   Microsoft Azure experienced a power event at their France Central datacenter, caused by a loss of utility power from an external provider. Power has since been restored via backup generators and recovery is underway. As of now, there are no active disruptions to Viedoc services, and we continue to monitor the situation closely.

4. 27 Nisan 2026 19:00 UTCresolved

   This incident has been resolved.

1. 9 Aralık 2025 09:37 UTCinvestigating

   We have received reports of intermittent delivery failures affecting text messages sent to numbers with country codes +31 (Netherlands), +32 (Belgium), +33 (France), and +44 (United Kingdom). An investigation is currently underway together with the subproccessor. The default SMS sender is changed from a phone number to "Viedoc" to reduce the risk of texts being treated as spam.

2. 9 Aralık 2025 12:20 UTCresolved

   Since 10.30 CET today text messages are delivered as expected to numbers with country codes previously listed.

1. 5 Aralık 2025 12:25 UTCidentified

   The User Administration Log (Excel) and Log of Users and Roles (PDF) cannot currently be generated for studies containing more than 100 users. This issue was introduced in the 4.90 release and affects all instances where version 4.90 has been deployed. The root cause has been identified, and a corrective fix is currently in preparation.

2. 9 Aralık 2025 08:30 UTCidentified

   A fix has been developed and is currently undergoing testing. The fix is planned to be deployed as a hotfix.

3. 16 Aralık 2025 15:18 UTCresolved

   This issue has been resolved with the release of Viedoc 4.90.1, which was deployed to all production instances on 2025-12-16. The User Administration Log (Excel) and Log of Users and Roles (PDF) can now be generated as expected, including for studies containing more than 100 users.

1. 1 Aralık 2025 13:10 UTCidentified

   Since around 12.30 CET, 1st of December, Viedoc is not sending any emails from the EU and US training and production instances due to a service disruption. The issue has been identified and we are working with our subprocessor to resolve the issue. All emails triggered during the affected period have been queued and will be delivered. The incident is caused by a malfunction at one of our subprocessors.

2. 1 Aralık 2025 13:46 UTCmonitoring

   The email queue is currently being processed, and messages are being delivered, although with a temporary delay.

3. 2 Aralık 2025 08:21 UTCresolved

   The queue had been fully processed at around 9.20 PM CET on 2025-12-01. Since that time emails have been delivered without delay.

1. 25 Kasım 2025 13:31 UTCmonitoring

   Between 13:22 CET and 14:12 CET on 25 November 2025, Viedoc did not send any emails from the EU training and production instance due to a service disruption. The issue was identified and fully resolved at 14:12 CET, after which email processing resumed as normal. All emails triggered during the affected period have been queued and will be delivered. The incident was caused by a malfunction at one of our subprocessors.

2. 25 Kasım 2025 14:16 UTCmonitoring

   The email queue is currently being processed, and messages are being delivered, although with a temporary delay.

3. 26 Kasım 2025 09:08 UTCresolved

   The queue had been fully processed at around 5.30 PM CET on 2025-11-25.

1. 25 Kasım 2025 03:19 UTCresolved

   Operational disturbance observed on the Chinese instance (clinic.viedoc.cn). Resolved

1. 11 Kasım 2025 11:55 UTCresolved

   The planned release of version 4.89 to the CN training and production instances has been cancelled due to unforeseen technical issues specific to the Chinese server environment. As the 4.90 release is already scheduled for December, we will proceed directly from version 4.88 to 4.90 for the CN training and production instances. The impact to end users is minimal, as version 4.89 contains only non-critical bug fixes. No other instances or regions are affected by this change. We appreciate your understanding and apologize for any inconvenience this may cause.

1. 3 Kasım 2025 13:27 UTCresolved

   From approximately 23.44 UTC to 23.54 UTC, users faced issues logging in to the European production instance. Investigations to find the root cause are ongoing. No other instances were affected.

2. 10 Kasım 2025 10:45 UTCpostmortem

   Description From approximately 23.44 UTC to 23.54 UTC on 2025-11-02, users were unable to log in to the European production instance. It is possible that users faced sporadic issues logging in also between approximately 23.00 UTC and 23.44 UTC. No other instances were affected. ‌ Cause The cause of the issue was an unexpected error in the identity provider \(idp\), leading to an accumulating memory consumption during the evening \(UTC\) of 2025-11-02. From approximately 23.00 UTC users would face sporadic failures when trying to log in. From approximately 23.44 UTC users could not log in. At 23.54 UTC on 2025-11-02 the idp was restarted, and users could log in as expected again. ‌ Corrective Action Alerts were triggered when the idp did not respond and the idp was restarted again at 2354 UTC on 2025-11-02. After the restart users could log in as expected again. ‌ Preventive Action Preliminary investigation identified a few improvements that could be made to make the idp more resilient. Implementation of these improvements have been initiated while the investigation of the issue continues.

1. 2 Eylül 2025 13:56 UTCinvestigating

   Emails triggered from EDC actions in Viedoc has been failing sporadically on the EU production instance since approximately 9AM CEST 2025-09-02. No other instances are affected. Investigations are ongoing.

2. 3 Eylül 2025 08:49 UTCidentified

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

3. 3 Eylül 2025 11:25 UTCmonitoring

   A fix has been implemented and emails are now being sent as expected. We will continue to monitor the situation.

4. 3 Eylül 2025 14:27 UTCresolved

   Since approximately noon CEST, emails triggered from the EDC has been delivered as expected.

5. 9 Eylül 2025 20:22 UTCpostmortem

   **Description** Between 9AM CEST on 2025-09-02 and noon CEST 2025-09-03 there were sporadic failures in email alerts expected to be triggered from Viedoc on the EU production instance. No other instances were affected. Customers were initially informed through the status page at 15.56 CEST on 2025-09-03. ‌ **Cause** On Tuesday at 9AM CEST on 2025-09-02, there was a very high load on the system. The high load on the system caused worker function apps, used to handle various processes  in the EDC, to scale out to the maximum use of 20 instances in parallel. This caused failures, and in combination with in-built retry policy of failing actions, there was an overload on the system. While form save and form view continued to work as expected throughout the duration of the issue, there were sporadic errors in specific system actions in the post-processing step. * EDC email alerts, configured in the CRF design, were sporadically not sent during this time window. It did not affect all emails. * Terms defined to be coded in the medical coding tool sporadically failed to sync to Viedoc Coder. It did not affect all terms. ‌ **Corrective action** Once the root cause of the exceptions was identified, the worker function app was gradually scaled down to run on 4 instances to avoid having too many actions ongoing at the same time. This work begun around 11AM CET on 2025-09-03 and an immediate improvement could be seen. Around noon 2025-09-03 the situation was completely resolved, and all emails could be sent as expected again. ‌ Email alerts not sent during this issue could not be re-sent and will also not show up in the communication log. ‌ All terms that had not synced properly with Viedoc Coder during the issue, were synced with Viedoc Coder on the afternoon of 2025-09-03 and 2025-09-04. ‌ **Preventive action** Scaling down the worker function app to run on 4 instances is not considered to bring any noticeable impact on performance, but will ensure the same overload issue will not occur again. An evaluation will be performed if it is necessary to scale up the worker function app again and if so, how this could be done without causing any similar issues.

1. 25 Ağustos 2025 11:29 UTCinvestigating

   When exporting custom reports in xptv8 format through Viedoc Reports, and using an %xpt2loc macro to import the data to SAS, the macro can fail when using long labels for columns. Investigation is ongoing.

2. 28 Ağustos 2025 13:11 UTCresolved

   The issue has been resolved with a hotfix on Viedoc Reports. When exporting custom reports in xptv8 format from Viedoc Reports, using an %xpt2loc macro to import the data to SAS will now work as expected also when using long labels for columns.