Conversation
There was a problem hiding this comment.
Pull request overview
Adds the release notes entry for version 1-299-0 to the collections/_release-notes documentation set.
Changes:
- Introduces a new 2026-04-16 release notes markdown file with
productupdatesfront matter. - Documents a set of bugfixes (SDK cron scheduling, claims field behavior, and multiple UI fixes).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <span class="tag-bugfix">bugfix</span> | ||
|
|
||
| - We've improved the accuracy and resiliency of cron scheduling for plugins in the Canvas SDK. They should now fire much closer to the minute boundary, as well as address cases where tasks that fire every minute could rarely fire twice or not at all. | ||
| - Fixes an issue where icn_dcn_1 field is incorrectly sent for claims that are not resubmissions. |
There was a problem hiding this comment.
For readability/consistency with other release notes, consider adding “the” and formatting the field name as code (e.g., “the icn_dcn_1 field ...”).
| - Fixes an issue where icn_dcn_1 field is incorrectly sent for claims that are not resubmissions. | |
| - Fixes an issue where the `icn_dcn_1` field is incorrectly sent for claims that are not resubmissions. |
| - Fixes an issue where icn_dcn_1 field is incorrectly sent for claims that are not resubmissions. | ||
| - In some circumstances the scheduled status of a drug would disappear from the UI once a pharmacy was selected. This has been resolved. | ||
| - The banner that warns of unsupported browser usage was sometimes hidden. This has been resolved, and if the user is using a browser other than Chrome they will see the unsupported browser banner. | ||
| - The patient search results were not scrollable, so it was hard to navigate when there were many reasons (for a common last name, for example). This has been addressed by making the results scrollable. |
There was a problem hiding this comment.
“many reasons (for a common last name, for example)” reads like a word mix-up; it likely should be “many results” (or similar) since this is describing search results volume, not reasons.
| - The patient search results were not scrollable, so it was hard to navigate when there were many reasons (for a common last name, for example). This has been addressed by making the results scrollable. | |
| - The patient search results were not scrollable, so it was hard to navigate when there were many results (for a common last name, for example). This has been addressed by making the results scrollable. |
|
|
||
| <span class="tag-bugfix">bugfix</span> | ||
|
|
||
| - We've improved the accuracy and resiliency of cron scheduling for plugins in the Canvas SDK. They should now fire much closer to the minute boundary, as well as address cases where tasks that fire every minute could rarely fire twice or not at all. |
There was a problem hiding this comment.
The sentence uses an awkward construction: “..., as well as address cases ...”. Consider rephrasing (e.g., “..., and addresses cases ...”) to make the grammar clear and avoid implying the cron jobs themselves are doing the “addressing”.
| - We've improved the accuracy and resiliency of cron scheduling for plugins in the Canvas SDK. They should now fire much closer to the minute boundary, as well as address cases where tasks that fire every minute could rarely fire twice or not at all. | |
| - We've improved the accuracy and resiliency of cron scheduling for plugins in the Canvas SDK. They should now fire much closer to the minute boundary, and this also addresses cases where tasks that fire every minute could rarely fire twice or not at all. |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
No description provided.