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: Sep 3, 2026
September 4, 2026
Release Number: 26R2.0.6
| Category | Description | Issue No. |
|---|---|---|
| MyVeeva | MyVeeva Users | Some participant surveys that were opened and completed on an iOS device at specific time points during the 26R1 release process and that are saved on the device were not sent to the server upon submission. | MYVC-54445 |
| MyVeeva | MyVeeva Users | Rarely, when a respondent completes a survey on an iOS device, the survey may not automatically advance when expected. This issue can occur when the survey uses cascading validation expressions for single choice or number scale questions and the respondent answers a question in an invalid way, then changes a previous answer in a way that makes the dependent answer valid. The dependent question's status does not update and prevents the participant from advancing. | MYVC-52839 |
| MyVeeva | MyVeeva Users | When a participant attempts to sign an eConsent document out of order on an iOS device, a generic error message is displayed instead of a signing conflict error. | MYVC-53354 |
| MyVeeva, eCOA (Sites) | MyVeeva Users, Site Staff | In rare scenarios, when Site Staff activate a new study version and the system processes many changes, the system may fail to start schedules and make surveys available. | MYVC-54191 |
| eCOA (Sites), Study Home | Site Staff, Sponsor/CRO Staff | When Site Staff make a data change to a single part survey that adds a new row of data, the Survey Data report tracks information and uses formatting that should only be included for multipart surveys on that new row. The QSCATGID column is added and an unnecessary trailing colon is added to the display label in the QSCATDIS column. | MYVC-54636 |
August 28, 2026
Release Number: 26R2.0.5
| Category | Description | Issue No. |
|---|---|---|
| MyVeeva | MyVeeva Users | Respondents can access and submit a survey that should no longer be available after a time zone change. | MYVC-53716 |
| MyVeeva | MyVeeva Users | In certain time zones during specific time periods of the year, the system stops recurring surveys from becoming available if the start event datetime for those surveys was set prior to that time period in a different time zone. This issue occurs because of a mismatch between internal time zone databases. | MYVC-53489 |
| Studio | Sponsor Staff | When a site user removes a survey that contains a siteMedia block with an optional answer, the system does not update the Survey Compliance status and reports and it is not removed from the Survey Compliance calculations in Study Home. Study Home data is also not updated when a site user performs a data change for an optional siteMedia answer. | MYVC-53555 |
| Studio | Sponsor Staff | Rules may not trigger as expected for surveys that have parts. This issue occurs because the system does not add the part name column in the collection rule trigger database table. | MYVC-54563 |
August 21, 2026
Release Number: 26R2.0.4
| Category | Description | Issue No. |
|---|---|---|
| eCOA (Sites) | Site Staff | When a rule only includes invalid email addresses, it causes notifications to incorrectly be sent to all site users instead of being blocked. | MYVC-54437 |
| eCOA (Sites), MyVeeva, Study Home | MyVeeva Users, Site Staff, Sponsor/CRO Staff | When Sponsor/CRO and Site Staff view screenshot reports with surveys that include a number scale question type, the system displays the incorrect numeral format for Bengali and Marathi languages. When Site Staff and MyVeeva Users view and complete surveys that include a numeric rating scale question type, the system displays an incorrect numeral format for Assamese. | MYVC-54172 |
| MyVeeva | MyVeeva Users | When a MyVeeva User quickly completes and submits an as-needed survey, the survey submission may fail. This issue occurs because the system is still creating the survey record when the MyVeeva User attempts to submit it. | MYVC-52939 |
| MyVeeva | MyVeeva Users | When Site Staff change the start event date for a participant on a recurring survey with reminders, the scheduled recurring surveys are canceled. If the participant opens an iOS or Android notification reminder previously sent for a survey that is now canceled, the system allows them to complete and submit that survey. This issue occurs when there are two or more previously available surveys that are now canceled and the participant opens the notification from the second (or later) canceled survey in the sequence. | MYVC-52990 |
| MyVeeva | MyVeeva Users | When an eConsent with a PDF source has fillable fields, required text entry, checkbox, or single select questions are not displayed in the eConsent viewer in a browser. Participants cannot sign the form because the required question is blank. | MYVC-53558 |
| MyVeeva | MyVeeva Users | A participant cannot access an eCOA diary on the first scheduled day if the start event occurs after the daily end time. The system incorrectly makes the diary available on the following day. | MYVC-54238 |
| MyVeeva | MyVeeva User | When a recipient's email address for a rule-triggered notification has a leading or trailing space, the system treats the address as invalid and does not send the email. | MYVC-54336 |
| Studio | Sponsor/CRO Staff | This feature enables Sponsor/CRO Staff to generate screenshot reports with all screenshots taken using a tablet-sized screen. Sponsor/CRO Staff can choose to generate screenshot reports in either the default sizes (phone for ePRO and tablet for eClinRO) or all in the tablet size. | MYVC-53478 |
| Study Home | Sponsor/CRO Staff | When a failed backend migration affects compliance data in a sandbox study, Sponsor/CRO Staff receive an error when opening the compliance dashboard because related survey records are missing survey types. | MYVC-54343 |
August 14, 2026
Release Number: 26R2.0.3
| Category | Description | Issue No. |
|---|---|---|
| Study Home, Studio, eCOA (Sites) | Sponsor/CRO Staff, Site Staff | When a participant name, survey label, site number, export job name, or study group label is made up only of digits and is larger than 2,147,483,647, filter dropdown options fail to load in Study Home (including the Compliance Dashboard) and the site experience Past Surveys list. Sponsor/CRO Staff are also prevented from creating new study groups with equally long labels. | MYVC-54164 |
August 12, 2026
Release Number: 26R2.0.2
| Category | Description | Issue No. |
|---|---|---|
| eCOA (Sites) | Site Staff | When Site Staff attempt to apply individual or bulk signatures to completed composite or multi-part surveys, the signature process fails. The system displays an error and does not save the signatures. | MYVC-52025 |
| eCOA (Sites), Studio, Study Home | Site Staff, Sponsor/CRO Staff | During the 26R2.0 release window, if a site region was not upgraded before the customer region was upgraded, surveys that were submitted and successfully stored in that site region were not processed for reporting. As a result, impacted survey response and adherence data was not displayed in Study Home or Survey Data, Compliance, and Audit Trail reports. This hot fix resolved the problems with impacted survey submissions and they are now displayed as expected in Study Home and reports. | MYVC-54137 |
August 10, 2026
Release Number: 26R2.0.1
This release includes updates to internal Veeva tools.