Maintenance releases fix issues that affect customers in production environments. We typically document the release at least twenty-four hours before the deployment. This list documents only fixes to general releases, and the list of fixed issues is not finalized until just before the deployment.
The issues below are now fixed. See the eCOA section on the Known Issues page for page for additional issues that staff and MyVeeva users may encounter.
Last Updated: May 27, 2026
May 29, 2026
Release Number: 26R1.0.10
| Category | Description | Issue No. |
|---|---|---|
| eCOA | Sponsor/CRO Staff | When sponsor/CRO staff delete a draft collection version, create a new version, and start UAT, the system is unable to transition the status to UAT in Progress. The collection remains in Draft status. | MYVC-51275 |
| eCOA | Sponsor/CRO Staff | When sponsor/CRO staff update survey translations in a new version of a collection without modifying the survey, the screenshot report does not include the updated text. The screenshot report continues to display the translations from the previous version of the collection. | MYVC-51313 |
| eCOA | Sponsor/CRO Staff | When sponsor/CRO staff export survey data, the system displays blank QSCATID and QSLANG columns for calculated scores in surveys that do not have multiple parts. This issue affects data submitted after the 26R1 release. | MYVC-51156 |
| eCOA | Sponsor/CRO Staff, Site Staff | When site staff remove a completed survey that has scores, the audit trail sometimes records a system audit for UPDATE_SURVEY_SCORE with an incorrect timestamp of 1970-01-01 00:00 or in addition to the expected audit with the actual removal time. The user's removal action itself is audited with the actual removal time. | MYVC-51419 |
May 22, 2026
Release Number: 26R1.0.9
| Category | Description | Issue No. |
|---|---|---|
| MyVeeva | MyVeeva Users | The MyVeeva for Patients application may crash on Android devices when a participant reopens it after viewing a PDF consent form. This occurs when the operating system reclaims memory while the app is in the background. | MYVC-50374 |
| MyVeeva | MyVeeva Users | For participants using Android devices, the MyVeeva for Patients application performs excessive background caching of surveys that have not started. This repeated caching uses too much of the device resources and data. | MYVC-50666 |
May 22, 2026
Release Number: 26R1.0.8
| Category | Description | Issue No. |
|---|---|---|
| eCOA (Sites) | Site Staff | Site staff encounter an error when they attempt to move a survey to an event that is already associated with the survey. This occurs when the user accesses an outdated view of past surveys or has multiple browser tabs open. | MYVC-50292 |
| eCOA | Sponsor/CRO Staff | When sponsor/CRO staff attempt to deploy a collection version that contains a large number of schedules, the deployment fails. The system cannot complete the deployment because the data size for the schedules exceeds the internal message limit. | MYVC-51279 |
| MyVeeva | MyVeeva Users | Participants can now successfully reset their password during an In Person session. Previously, the system displayed an error because it attempted to retrieve time zone settings before the participant was authenticated. | MYVC-51235 |
| eCOA | Sponsor/CRO Staff | In eCOA Studio, the system displays a validation error for sponsor/CRO staff when they configure a section condition controlled by a block in a different section but in the same survey part. The system incorrectly identifies the sections as belonging to different parts. | MYVC-50101 |
| eCOA (Sites) | Site Staff | Completed surveys are now accessible for site staff through the survey label link in rule-triggered email notifications. Previously, the system used an incorrect ID format for the links, which prevented the surveys from opening. | MYVC-51346 |
May 8, 2026
Release Number: 26R1.0.7
| Category | Description | Issue No. |
|---|---|---|
| eCOA | Sponsor/CRO Staff | This update increases the configurable offset value to a maximum of 36,526 days for anchored events to support extended study timelines. | MYVC-50797 |
| eCOA (Sites) | Site Staff | This update ensures that site staff can backdate event dates and times up to three years in the past. | MYVC-50796 |
May 4, 2026
Release Number: 26R1.0.6
| Category | Description | Issue No. |
|---|---|---|
| MyVeeva, eCOA | MyVeeva Users, Sponsor/CRO Staff, Site Staff | When a participant's iOS device has incorrect data that was previously cached and they submit a survey, the system may associate the responses with a future survey instance. This causes the submitted survey task to remain Available in the participant's task list and the completed survey record to have an inaccurate First Available At timestamp in the system. | MYVC-50714 |
May 1, 2026
Release Number: 26R1.0.5
| Category | Description | Issue No. |
|---|---|---|
| Study Home | Sponsor/CRO Staff, Site Staff | Sponsor/CRO Staff cannot see data change requests in Study Home when Site Staff request a data change for a survey that is started by an event that was updated in minor versions of the collection. | MYVC-50522 |
| eCOA (Sites) | Site Staff | Survey completion notifications are not sent to Site Staff for participants who are connected to a SiteVault study. | MYVC-50461 |
| Studio | Sponsor/CRO Staff | Deployments fail in UAT sandboxes when increasing from a minor to a major version (for example, 4.1 to 5.0). | MYVC-50415 |
| MyVeeva | MyVeeva Users | For participants using Android devices, the system may sometimes fail to Save survey responses. | MYVC-50635 |
April 28, 2026
Release Number: 26R1.0.4
| Category | Description | Issue No. |
|---|---|---|
| eCOA | MyVeeva Users, Sponsor/CRO Staff; Site Staff | On iOS devices, the application sometimes saved a survey submission incorrectly, which caused the system to record the survey response under a future scheduled survey instance that wasn't available yet, instead of the presently due survey. | MYVC-50451 |
April 27, 2026
Release Number: 26R1.0.3
| Category | Description | Issue No. |
|---|---|---|
| MyVeeva | MyVeeva Users | When a participant using the iOS app submits a survey, the system may associate the responses with a future survey instance. This causes the submitted survey task to remain Available in the participant's task list and the completed survey record to have an inaccurate First Available At timestamp in the Compliance report. | MYVC-50455 |
April 24, 2026
Release Number: 26R1.0.2
| Category | Description | Issue No. |
|---|---|---|
| Study Home | Sponsor/CRO Staff | When Sponsor/CRO Staff access the Study Home dashboard, the system may display an outdated collection version for some sites after a new version is deployed to them. This issue also occurs when the version is set to automatically activate for sites after deployment. | MYVC-50278 |
April 20, 2026
Release Number: 26R1.0.1
This release includes updates to internal Veeva tools.