For all the people experiencing cache invalidation failures – can you please edit your website setup records and just re-select the touchpoints and web applications and then save the record?

I did this already, and it's not working constantly

OK, well I would recommend raising cases

Yes, I did create one: #6631689

Worked on my end!

yes.. it's not working consistently..

is not working for several customers either

@Martin tell your customers to create cases, there's a defect already #851854

We're piling on this defect # this morning. fingers crossed

Got it upgraded to a U3 no less

Thanks!

I did nothing. It was all the cases being attached, highlighting that it had a broader blast area than previously suspected. If you see me encouraging you to raise cases, it is because it raises an issue's profile. This is an example of that.

image.png

@Steve Goldberg I think your recommendation is correct on creating cases and you are doing what you can, thank you! However: Can we, one day, agree that customer reporting issues doesn't necessarily match the real-world urgency of an issue? IE issues with network or SEO engine. Very hard to detect by regular users, but critical. This should be proactively monitored and never lower than U3 by default. It is just platform reliability, isn't it? How can platform reliability be defined by how many cases are created?

Can we, one day, agree that customer reporting issues doesn't necessarily match the real-world urgency of an issue?

We don't disagree about it now. What we might disagree about, however, is whether I have the power to affect this change

Oh I know, I'm fully supportive of what you are doing with the tools you have 🙂 Is there anything we can do as a community to "make it happen" all together? Happy to put some of the effort @Steve Goldberg