Maintenance

On March 24th, 6:00 AM CT, our team will migrate our primary DNS from the old infrastructure to the new one. This change may cause the server to be intermittent or offline few a few minutes. We expected the maintenance window to last around 1 hour, ending at 3/24 7:00 AM CT.

Update: To ensure a smooth transition over to a new server infrastructure, we are running additional rounds of tests internally. We decided to postpone this release for another week due to March 17th, 7:00 AM CT.

Howdy!

Shopify recently introduced a set of changes to their checkout experience that require an update on how our extension integrates with your store. To account for those changes and to create a more stable and reliable experience for you, on our next release on 3/10, the ...

Update 5: API functionality restored. We are still working on deploying the new infrastructure fully but that should happen transparently. We are currently investigating issues with case assignment and webhooks. ETA for complete deployment is 1:00 PM CT, although we expect services to be functional already. We apologize for the inconvenience.

Update 4: We are currently experiencing two unexpected issues with conflicting security policies and data migrations taking longer than expected t...

We are rolling out a few fixes and improvements today with no expected downtime. That's to accommodate our upcoming MDI Preferred Profile Program and a few additional fixes.

Next Monday we'll be rolling out a few fixes and improvements across different products with no expected downtime. The reason for the short notice is to expedite the release of a pharmacy integration to enhance our capability of prescribing weight loss medication.

[Features]
- New API integration with Boothwyn pharmacy

[API]
- Introduced a new dynamic offering type to support Boothwyn integration and other offerings in the future
- Changed the name for auto generated PDFs to be more human...

Database upgrade was successful. We'll be monitoring to see if timeout issues are reduced going forward.

A database server upgrade may require restart, which may cause temporary service disruption for a few minutes. This upgrade is required to mitigate the timeout issues the platform has been experiencing. We apologize for the inconvenience.