It lists all instances, you can drill down into each one of them, see which services are affected, and each affected service pops up the incident timeline?
Isn't it actually amazing, and not "the most salesforce thing ever"?
"And in tonight's news, the worldwide CRM solution Salesforce had a global outage affecting one hundred percent of its customer base. We interviewed users of the service to find out the scope of the impact. Everyone agreed that they were impacted, but strangely, nobody could describe _in what way_ they were affected."
There is a published sticker price, but I don't think anyone outside of tiny installs with just a few users pays that... it's very much the enterprise sales model of "let's schedule a call and talk about it." They also for many years would let previously negotiated prices stand during renewals even when sticker price went up, so older orgs often have the "same" license being charged at many different prices based on when it was first purchased and how the negotiations went at the time.
And nothing of value was lost. God, I hate everything about Salesforce. Sometimes I have to integrate against their services, and it is always a pain, not to mention what the core project actually is: optimization of marketing and spam.
Sandboxes drift from production in both metadata and data. Refreshes change record ids.
API access is gated by edition. Professional edition has none by default. Salesforce sells MuleSoft as the fix to their own shit architecture.
Custom objects and fields mean that connecting successfully doesn’t establish what represents a customer, subscription or completed sale. Even standard objects can be used differently between organizations.
Metadata deployment is SOAP-based and slow. Dependencies between components break deploys and is massive pain to debug.
And notice that I said integration, not API integration. There’s a shit storm of terrible way to integrate beyond just simple API. Have fun with Bulk 1 or 2, Composite, Streaming, Platform Events, Change Data Capture, Tooling, GraphQL. An my most hated item, anything web based.
I seriously want to talk to someone that have a good time integrating against Salesforce. Maybe I will have my mind blown as to how easy it could be, but I suspect I will have the same experience I have every time I critical scrutinize and such situation: it’s just as terrible as it seems and the person claiming it’s easy is hands down producing close to nothing of value.
> Sandboxes drift from production in both metadata and data. Refreshes change record ids.
I find it odd you would expect sandboxes to not drift and record ids to not change on refreshes. People are working on sandboxes so they will naturally diverge from production, same for record ids.
Refreshes mean that data will be wiped out so you have to preserve the data you want first, then restore it after the refresh. Isn't that the same with any other database where you dump a copy of production on an instance?
I don't see a difference between custom objects in SF and any plain SQL database table that needs to be changed to accommodate a new requirement.
Dependencies between components break deployments - isn't that universally true?
What are other platforms where such things don't happen?
My gut instinct is that this is about when all of their on prem servers were EOL and their /public cloud solution was required. This must have had something to do with that
This might actually be one of the most useful status pages ive seen. Its not just random green tick marks representing the entire service that only change yellow when someone gives and admits that 5 hours of bad service is an outage.
You can click on any of the instances and then the service that is down to read the updates. It’s not 100% clear but some sort of issue with a “legacy login service”. The latest updates say a fix is rolling out.
176 comments
[ 3.2 ms ] story [ 98.9 ms ] threadScroll down. >_<
Isn't it actually amazing, and not "the most salesforce thing ever"?
Now I'm just glad I'm not responsible for this fire
/s (partly)
But if you’re having trouble with the standard rest or bulk apis, that’s 100% on you.
Salesforce API?
Sandboxes drift from production in both metadata and data. Refreshes change record ids.
API access is gated by edition. Professional edition has none by default. Salesforce sells MuleSoft as the fix to their own shit architecture.
Custom objects and fields mean that connecting successfully doesn’t establish what represents a customer, subscription or completed sale. Even standard objects can be used differently between organizations.
Metadata deployment is SOAP-based and slow. Dependencies between components break deploys and is massive pain to debug.
And notice that I said integration, not API integration. There’s a shit storm of terrible way to integrate beyond just simple API. Have fun with Bulk 1 or 2, Composite, Streaming, Platform Events, Change Data Capture, Tooling, GraphQL. An my most hated item, anything web based.
I seriously want to talk to someone that have a good time integrating against Salesforce. Maybe I will have my mind blown as to how easy it could be, but I suspect I will have the same experience I have every time I critical scrutinize and such situation: it’s just as terrible as it seems and the person claiming it’s easy is hands down producing close to nothing of value.
I find it odd you would expect sandboxes to not drift and record ids to not change on refreshes. People are working on sandboxes so they will naturally diverge from production, same for record ids.
Refreshes mean that data will be wiped out so you have to preserve the data you want first, then restore it after the refresh. Isn't that the same with any other database where you dump a copy of production on an instance?
I don't see a difference between custom objects in SF and any plain SQL database table that needs to be changed to accommodate a new requirement.
Dependencies between components break deployments - isn't that universally true?
What are other platforms where such things don't happen?
(Nowadays any of those need to fit in an "agent dropped all tables. Apologized" moment.-)
Salesforce goes down.
No causation here...move on.
At least salesforce is consistent with their design language
It has a search that works well.
When you click on an instance it shows what service is down and has a log of updates that come in roughly every 30 minutes.
The instance status URL is predictable so runbooks could already be prepared with deep links.
It even has a text box for email updates.
What more do you want exactly?