:( Something has gone wrong

[marcusquinn]

The message says:

Something has gone wrong

This app is currently not responding. Try refreshing the page.

That might have seemed cute at the time, but for the uninitiated, it implies failure on more levels than just the app, but the implementor, host and anything else by association. It's just negative all round.

May I suggest:

Restarting...

This app should be back shortly. Please try refreshing the page.

If it's still not working in a few minutes, please check with your support contact.

[girish]

@marcusquinn alright, I replaced it with

[fbartels]

@marcusquinn said in Something has gone wrong:

with your support contact

That part sounds kind of strange to my non-native speaker ears. But i am also not sure how to phrase it better.

With your administrator

With your local it support

Ask your supervisor

Edit: or maybe even start earlier in the sentence

Instead of

please check with your support contact.

Please contact your it support.

[girish]

or maybe just "please contact support" ? and let the user figure out? alternately, I can drop that line altogether I guess.

[subtlecourage]

@girish
Please contact support and hyperlink the email that the cloudron admin can change?

[marcusquinn]

@girish Brilliant - thank you kindly. That covers a more positive spirit.

Proof-reading and more subtle wording nuance to make everyone happy is appreciated but my work here is done

[marcusquinn]

@subtlecourage I worded it generically without the need for variables to edit on purpose, as I think that having it editable would have been a bigger ask. No reason why it couldn't be a Cloudron setting to configure too - but that's up to @girish on the time/value triage.

[marcusquinn]

Are we waiting on a release for this update?

Negative sentiment weighs heavily when users can take opportunity to blame systems for things when they aren't alive throughout the day - and frustratingly I am battling an issue with an app in production that needs many restarts per day because or errors that are not showing in any logs anywhere.

[marcusquinn]

Nudge - frustratingly on this, our live production users are getting this message several times a day - the negative sentiment towards the systems grows every time.

I see this as an urgent issue because the time-costs of user push-back against new systems can be severe and swift.

I need to focus time on debugging the cause of the issues, but there is unnecessary extra overhead in diplomacy explaining that the system won't always be "going wrong" and that is ti a system in development, so it's not really wrong at all, it's actually being made better many times a day.

[nebulon]

@marcusquinn understood, and the release takes a bit to long also from out perspective, but we also don't want to risk other side-effects by pushing it out prematurely.

[marcusquinn]

@nebulon Gotchya, thanks - I have to vent somewhere

[robi]

@marcusquinn sign up for the beta and help test

[marcusquinn]

@robi where's that?

[nebulon]

@marcusquinn there is no beta program. The current rollout is, that we provider updates to all users over a span of a few days to a week, BUT once the release is out, everyone can manually check and thus apply the update.

[marcusquinn]

@nebulon Ahhh @robi was making a funny