@Steve Goldberg @Mike Lynch Hey, I have an issue with Facets and Price levels in 2019.1. I've got the price levels (and online price) in the configuration with correct range type and templates but also have them as facet and sort options in the website record as well. When i try to filter by price, it comes up with Internal Error Search Failed (as opposed to the nlsortoptions error if they aren't in there at all) Is there something I am missing? As its not working for a customer with a price level (the facet filter shows still - named differently so i know its the price level range one) and then also with no customer logged in which should use the online price.

Hey @Applejack Group - do you have the pricelevel for the logged in customer setup as both a facet and a sort option? I sometimes get this stuff when I have "onlinecustomerprice" setup as a facet and a sort option but not "pricelevel2" or whatever the specific customer is meant to be using

Hey @Mike Lynch, yep ive got them all there. Weird thing is even with no customer logged in, i cant get it to work now on the default online price range facet? Coming up again with internal error search failed

Ah OK - I'm actually seeing the exact same thing on my demo accounts now... Just going to check on stuff and see if anyone internally knows about it yet

@Mike Lynch Just updating now. I was on 2019.1.2.... So there is a good chance this might fix it. 🙂 Thank you for mentioning the bundle updates as I didnt even think to consider a patch had been applied (or that it hadnt been auto applied - realising its not managed)

Awesome. I love when stuff works! ...and when you don't have to log a ticket

Hi Mike I'm seeing the same Issue in production. I'm using 2019.2. If I update the bundle does it have any impact on existing SCA source code changes?

@Charan - Sorry, are you using 2019.2? or 2019.1.2? If it's 2019.1.2, then you can just update the core bundle underneath your theme and extension and it will be fine - so long as you haven't modified the core SSP application of course. I haven't seen 2019.2 yet, so I hope you meant 2019.1.2!

Yeah, I don't think anyone has 2019.2 so I'm guessing he's mistaken.

Is there a documented update patch related to this issue?

I'm unsure about this issue but Mike said earlier that it was resolved in a newer version of 2019.1, so I think updating the bundle and thus your site's source should do it

Mmm... I updated the core, and still getting this error --- "{"errors":"Search failed","code":400,"warnings":{}}"

@wbermudo Which version have you updated to? I think it needs to be at least 2019.1.4 (latest is 2019.1.5) to have the fix. If you*are* on the latest version, just try invalidating your cache maybe?

@Mike Lynch Thanks for getting back, I updated to the latest version 2019.1.5 and did cache invalidation, and rebuild of search index, still no luck, getting "Search Failed", code 400 error.

Just on the price range slider? Or is it happening on any other facets?

the whole product list page, it's not working - "Internal Error" search failed.

OK, that's a different issue - the start of this thread was about the price slider! What you're seeing there could be an invalid search index

yep, thought it was the same issue. No luck on the rebuild and I already max-out the rebuilds but didn’t work. Anyways thanks for your time looking at it, I really do appreciate it. I filed a support case.

Hey @wbermudo - I'm not sure if it's relevant or if you've already solved your issue via support, but I saw this SuiteAnswer https://netsuite.custhelp.com/app/answers/detail/a_id/85091 which has to do with old content from CMS v 2 not being deleted properly after updating to CMS v 3. Did you by any chance upgrade your new site from an olde version?

@Mike Lynch- thanks for the update, my issue is related to the product list page when it is hitting the items API, it just fixed itself overnight not sure what happened. Though there is one thing I can think of, right now our data team is importing (create/update) hundred thousands of items, I think it's making the SCA items database kind of choke??, I think the rebuild search index did not work since there are constant single item update re-indexing. I'll monitor this issue in the coming days, and will keep you posted if I find anything. Thanks again Mike!

OK that's weird. What's the case number for this?

Yes, I thought so too.. It's Case #3523546, thanks again..

No, thank you. I'm going to ask the tech pubs team / dev team to make amendments so that this doesn't happen again

Hi @wbermudo Did you get any response from the support regarding this price slider Internal error Issue. Because we are facing the same Issue in our account as well since we are using 2019.1.5. Upon checking we have structure delimiter in Image setup as "." but still we are seeing the error.