Hey everyone,
I wanted to follow up here about what happened. Firstly, I want to apologise for any surprise or frustration this caused. I want to be transparent about what happened and what we’re doing about it.
What we were trying to do:
As Connect approaches end of support, we have an obligation to give customers advance notice when an app may be running on an unsupported platform. Our plan was to roll this messaging out to non-public apps first, deliberately giving our Marketplace partners more time to migrate before customers started seeing these notices.
Alongside that, we enabled the messaging in the Developer Canary Program (DCP) so enrolled partners and developers could:
-
Try out the new module ahead of a broader rollout
-
See the exact messaging customers will see and give you time to adopt the new module in your manifest before this messaging goes live
The intent was to strike a balance for both customers and partners, whilst giving you more space to migrate across to Forge and submit your migration status.
What went wrong:
Unfortunately, the communications we had planned to give partners advance notice of this change going live in canary instances did not go out as intended.
What you need to know:
-
This messaging was scoped to canary tenants only, we don’t expect anyone outside of this cohort to have seen this messaging
-
To address any concerns that you may have had, we pre-emptively raised an incident and there is a status page update you can point towards if you have any affected customers reaching out.
What will happen now:
-
For non-public apps:
- Today, we will restart the rollout of this change to non-public apps only in production*.* This will only include messaging in the admin experience and no end user notices. Development apps using a Connect app key which is not the same as the marketplace listing will see this messaging.
-
For public apps:
-
We will send out a changelog notice 1 week prior to us enabling this messaging for those enrolled in the developer canary program for early awareness. This will include messaging in the admin experience only. It will only appear for tenants enrolled in DCP. We are targeting a release date of June 2nd.
-
We will issue another changelog notice at least one week before this messaging goes live on production instances, giving you time to adopt the new module. We will target the rollout to start in July and gradually extend it to all public apps over three months. From September onwards, all customers with apps installed that use any Connect features will see this messaging in their admin experience and as end user notices in iFrames. Again, we will proactively communicate when the time comes to ensure you’ve made these changes and can share your migration plans with customers.
-
We apologise for any confusion or concern this caused, that was absolutely not our intention. We really value the partnerships we have built with this community and appreciate the effort you have put into your migrations.