GroveStreams
MikeMills private msg quote post Address this user
* Dynamic rollups in SQL fix for time zones that don't match what's in the component definition

* Query result grid fix for displaying issues when some column results don't have names
Post 201 IP   flag post
MikeMills private msg quote post Address this user
In a few days we are requiring stronger user passwords. This will not impact existing passwords.

Password strength will only be validated during new registrations or when a user changes their password. GS will return an error stating the password is weak and what the requirements are when a new password is being set.

Here are the new Pwd requirements:
Minimum 8 characters
Contain characters from three of the following four categories:
* English uppercase characters (A through Z)
* English lowercase characters (a through z)
* Base 10 digits (0 through 9)
* Non-alphabetic characters (for example, !, $, #, %)
Post 202 IP   flag post
MikeMills private msg quote post Address this user
* Strong passwords are now required during registration or when passwords are changed

* 90 day password expiration and two factor authentication (2FA) during sign-in options are now available

* Several Organization Notification glitches have been addressed such as being able to name a filter properly

* Component and Dashboard content store recovery added. Content store bugs can sometimes leave items hung where they still exist but can't be viewed. We've added logic during Component and Dashboard searches to identify and recover those items during a search. They will be placed under the root in a folder called Recovered. Only the org owner will see and have access to that folder.

* GS SQL schedule Repeat/NoRepeat option added:



* GS SQL leaves beta. More information here....
Post 203 IP   flag post
MikeMills private msg quote post Address this user
GS UI issues after the last patch? Clear your browser cache and refresh the page.
Post 204 IP   flag post
MikeMills private msg quote post Address this user
* Organizations can now mandate longer passwords

* Last "5" passwords not allowed

* "30" minute lockout after several password failures
Post 205 IP   flag post


MikeMills private msg quote post Address this user
* Fixed a GS SQL issue where the STREAM table column folderPath was not being updated for some component saves.

* Derivation performance improvements

* Daily stream compaction improvements
Post 206 IP   flag post
MikeMills private msg quote post Address this user
* Some SMS text messages are being dropped due to GroveStreams not having an approved SMS campaign registered with carriers.

* These carrier requirements are referred to as 10DLC

* We had applied earlier, but were rejected. We've made more compliance changes and have applied again.

* SMS will stop at the end of August for some carriers until we're approved.

* We apologize for the inconvenience

* Changes:
- Terms updated.
- opt-in added to user profile.
- STOP and START can be replied to an SMS.
- GroveStreams brand added to every SMS. This is added to every SMS now: Powered by GroveStreams. Reply STOP to unsubscribe.
Post 207 IP   flag post
MikeMills private msg quote post Address this user
GS's SMS carrier 10DLC application was approved today.

All SMS messages should be arriving now.

- For customers using GS Branding and don't want to see "Powered by GroveStreams" in text messages: Reach out to us, we are considering allowing customers to get their own SMS phone number which has been carrier 10DLC approved. There might be a fee associated with this depending on the solution we end up with.
Post 208 IP   flag post
MikeMills private msg quote post Address this user
* In the process of upgrading our network. HTTP response times have improved.
* Improved Derived Streams processing. Derivation cycles are running about 40% faster

* In the process of strengthening web server security. Your devices may be getting HTTP error code 400 if they are violating latest security standards. See this thread for more details.
Post 209 IP   flag post
MikeMills private msg quote post Address this user
* In the process of increasing the number of web servers and replacing our website load balancer to improve response times and stability

This will take place over the next few days.

All should be non-impacting to users, but there is a chance that changing the load balancer could disrupt website calls for a brief time (seconds or a minute or two).

Part of this process is testing load balancer failovers in a live environment. We'll post the times that we expect to make these types of risky changes.

The new load balancer will have the same ip address as our old one. No one should be hard coding the GS ip address in their devices as it could change someday.
Post 210 IP   flag post
MikeMills private msg quote post Address this user
We will be replacing our website load balancer on Friday July 7th, 2024 at 8 PM Central.

There will only be a few seconds of downtime for the website if everything goes as planned.
Post 211 IP   flag post
MikeMills private msg quote post Address this user
First attempt at replacing our website load balance failed. Small outage for about 5 minutes while we reverted back to the old LB.
Post 212 IP   flag post
MikeMills private msg quote post Address this user
We will be re-attempting to replace our website load balancer on Saturday July 6th, 2024 at 2 PM Central. We do expect a couple of minutes of downtime again while we try and diagnose the issue.
Post 213 IP   flag post
MikeMills private msg quote post Address this user
Second attempt failed as expected. Gathered more diagnostics and we're waiting for our server provider to analyze the results and schedule the next attempt.

They're trying to make our current IP address virtual so that we can assign it on the fly to two new LBs, a primary and a failover. A virtual test IP worked beautifully, but our current IP is being stubborn.
Post 214 IP   flag post
MikeMills private msg quote post Address this user
3rd attempt to replace our load balancer is at 7:00 pm tonight (July 11th). Site might be down for a couple of minutes if it fails again and we have to revert back.
Post 215 IP   flag post
MikeMills private msg quote post Address this user
4th attempt to replace load balancer is in a few minutes: Jul 15th 1:35 PM.

here might be a couple of minutes of downtime.
Post 216 IP   flag post
MikeMills private msg quote post Address this user
Load Balancer was swapped out. We've been sorting out some networking issues that impacted client initiated jobs like Reconcile.

Response times are a bit better as we've temporarily added some web servers. We'll be replacing almost every server with better servers over the next month.
Post 217 IP   flag post
MikeMills private msg quote post Address this user
Expecting zero down time as we continue making improvements. The high-risk changes are done.
Post 218 IP   flag post
MikeMills private msg quote post Address this user
* Strengthened SSL Cipher suite on one web server. Monitoring logs and customer responses before applying to all web servers.

Will not impact modern browser use. May impact devices passing data using the https api, but we monitored logs over the last couple of days and didn't see any devices using old ciphers.
Post 219 IP   flag post
2985 219 19
Log in or sign up to compose a reply.