Announcing Archer Platform Release 2026.04 Update Release 01 for SaaS

• 

  G

  June 26, 2026 11:06

  @Meg Oneil​ @Troy Helms​ 

  There are no Release Notes for 2026.04.01.

  Considering this is being deployed to Non-Production today and Production on Thursday, please update the release notes ASAP so we know what are the Fixed Issues as well as any new & changed platform features.

  Going forward Announcements should not be announced if Release Notes are not made available first...

  

  Originally posted on May 19, 2026.

  0
• 

  Alex Lahoski

  June 26, 2026 11:06

  I regret that I can only like this comment once. Release notes should be complete and available prior to, or at the time of release (at the latest).

  Originally posted on May 19, 2026.

  0
• 

  Meg Oneil

  June 26, 2026 11:06

  Earlier today, the release notes were published in the Help Center. Additionally, Archer SaaS Deployment and Communication FAQ is available to help clients better understand the timing of internal activities.

  Originally posted on May 19, 2026.

  0
• 

  G

  June 26, 2026 11:06

  I'm sorry to say but that's not good enough and change is needed and I don't think this is the first time I am raising this...

  Firstly, we are the customers, so if/when something goes wrong after a deployment Admins are the first one to get blamed and have to figure what happened and inform stakeholders at our organisation. Was it caused by the latest deployment? Is it an change that happened coincidentally at the same time? Who knows, but without any release notes, there's no power of deduction.

  Secondly, as per the link you shared it says 'Archer typically announces scheduled outage upgrades 1–2 weeks in advance to give clients time to prepare. However, the final release scope is often confirmed only shortly before deployment due to ongoing validation and final testing. As a result, finalized “What’s New” documentation or Help Center updates may be published after the initial announcement.' .

  I understand that as part of the actual deployment, variables may change and what was planned wasn't all deployed and that's why finalised documentation and updates are not available, but what about preliminary indication? What about planned fixes? Give us an idea of what you're looking to deploy and then once deployed confirm what was and wasn't deployed, what was fixed and what is still an issue. This prepares us as Admins to have an idea as to what to expect, so once the change is deployed if we see any strange behaviour we know straight away it attributes to the recent release and can raise a support ticket highlighting these defects to be resolved.

  I for one am based in the UK, so what makes things even more difficult is that:

  1. I received an email alert at 19:18 on Monday 18th May that an Update Release is coming BUT I didn't see this email until Tuesday 19th May morning at 08:45, at which point that was the window for deployment.
  2. I searched Archer Help Center and there was nothing, so now i'm in a predicament of do I continuing working on things in Development, should I wait just in case.
  3. I received an email alert at 14:29 Tuesday 19th May that there was an update and that Non-Production was completed.
  4. I searched Archer Help Center again and there was still nothing, so now I have a risk that users in Non-Production environments may incur issues and we don't know if that's expected or not.
  5. Wednesday 20th May morning, I see I have an email alert from Tuesday 19th May at 20:50 saying that Meg commented 'Earlier today, the release notes were published in the Help Center. Additionally, Archer SaaS Deployment and Communication FAQ is available to help clients better understand the timing of internal activities.'. So, finally the release notes are available but for me it's me a day after the deployment took place which isn't great.

  Lastly, the thing that really kicks me for this one is that only 2 things were fixed. No other changes, so surely that could have just been included in the SaaS announcement...

  I think as a tactical option, it would be appreciated to send an update out once Release Notes are available.

  The strategic and ultimate solution that would make all customers happy - release the release notes before (even if draft and subject to change = better than nothing).

  This is just me expressing why I believe it's beneficial to have preliminary/draft Release Notes before a change and how it impacts us customers if we don't have the data to hand. 😀

  Customers also feeling this pain: @Alex Lahoski​ @Alex M​ @Dawn Teply​ @Georgia Widjaja​ 

  Archer team for awareness: @Marius Chingaru​ @Maryann Klustner​ @Scott Hrubes​ 

  Originally posted on May 20, 2026.

  0
• 

  Yasmine Dowidar

  • Archer Employee

  June 26, 2026 11:06

  Test comment 4

  Originally posted on June 19, 2026.

  0

Please sign in to leave a comment.