Viedoc incident

Issues with data imports through the WCF API on the EU and US instance

Viedoc experienced a minor incident on October 10, 2024 affecting Background processes (import/export/revisions/alerts/archive/disposal) and Background processes (import/export/revisions/alerts/archive/disposal), lasting 6d 19h. The incident has been resolved; the full update timeline is below.

Started: Oct 10, 2024, 06:15 PM UTC
Resolved: Oct 17, 2024, 01:40 PM UTC
Duration: 6d 19h
Detected by Pingoru: Oct 10, 2024, 06:15 PM UTC

Affected components

Background processes (import/export/revisions/alerts/archive/disposal)Background processes (import/export/revisions/alerts/archive/disposal)

Update timeline

investigating Oct 10, 2024, 06:15 PM UTC

Imports of large data files submitted through the WCF API on the EU and US instance are currently failing. Investigation is ongoing and status updates will be provided here. For urgent imports, please contact the support or your product specialist for advice.
resolved Oct 17, 2024, 01:40 PM UTC

The issue has now been resolved. Imports of large data files submitted through the WCF API on the EU and US instances are now working as expected again. This issue was resolved on the EU instance on 2024-10-16 and on the US instance on 2024-10-17.
postmortem Oct 23, 2024, 06:41 AM UTC

**Description** After release of Viedoc 4.80, the WCF API did not accept requests with a large amount of data. This was for example causing the import of clinical data through the WCF API to fail. **Cause** When migrating the WCF service to dot NET core, the maximum size of message accepted was set to default \(65535 bytes\) in the framework. **Corrective action** Updated the code to change the message size to a configurable value. And changed the configurable value to accommodate large messages. ‌ **Preventive action** The message size is set to max value that can be handled by system.