Select to view content in your preferred language

What's in the upcoming (June 2025) release --

1156
13
06-23-2025 06:52 PM
JeffSilberberg
Frequent Contributor

 

I received a note that Velocity is down for upgrades later this week.  

It would be nice to know in advance what's changing so we know what to check on after the update!

 

As part of our upcoming release, your ArcGIS Velocity subscription will undergo a two-phase upgrade that will require scheduled downtime. The first phase will be updating the Velocity application to the latest release 2025.R2, and the second phase will be updating the data storage system:

- Phase 1 will begin on 06/26/2025 - 6 PM PST and is expected to last approximately 1 – 2 hours.
- Phase 2 will begin on 06/26/2025 - 6 PM PST and is expected to last approximately 1 - 3 hours (*).

* Some organizations with large volumes of data storage will require additional downtime during phase 2 and will be notified with further information.

Customer applications and workloads will be affected during both phases. You will receive a follow-up message once the upgrade is complete.

 

13 Replies
JeffSilberberg
Frequent Contributor

Esri Case #03942156

Both Organizations indicate they are running Version 6.02 but have very different "Home Pages".  

Also, I have completed upgrading Emails for all Velocity Instances, and then some. 

JMS - 

 

 

 

 

0 Kudos
JeffEismanGIS
Esri Contributor

@JeffSilberberg  I got to look at the support case and apologize for not understanding the question.  In this instance the utilization tab you are seeing on some pages and not in other is based on license level.  If you are logged in as a admin you will see utilization the others you will not have that visible.  

0 Kudos
JeffSilberberg
Frequent Contributor

@JeffEismanGIS 

I now understand that,  but the one missing Utilization is a custom role, and in this case, that seems to be impacting the display.   Support is still looking into it.  

 

0 Kudos
DrewDowling
Frequent Contributor

As test I tried to use the python api to stop a non functioning feed but that doesn't work either. The api reports the the feed is started. I call 

 feed.stop()

and the result is true but

feed.status

 still reports 'started'.