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 7, 2026
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.