Database errors on legacy Workfront search modules

[JohnJOSullivan]

Hi all,

I've noticed that some of my legacy search modules on one of my Scenarios have started failing. This Scenario is a biggie, but not the biggest one of our collection. The error message: [500] Database error due to invalid SQL statement.

The solve is pretty straightforward: Swapping to the newer search modules. But the thing which is mildly terrifying is that they're failing one by one at different intervals.

I try to reduce the number of search modules because I want to find all the data that I need pretty early on. That said, for some of our "Swiss Army Knife" style Scenarios, we need different search modules for different objects. 

Are other people noticing similar behavior from their search modules? I'm not going to lie, it's mildly terrifying--especially since I'm on vacation in a little over a week.

-j

[Lawson02]

I have not received this error yet. Maybe there is an invalid operator within the legacy search module. You could bring this up to support. I will come back to this thread if I ever see this error.

[IvanBebek-iX]

Hi @JohnJOSullivan, 

I agree with @Lawson02 this should be brought to support, I can see similar error was already reported few years ago https://experienceleague.adobe.com/en/docs/workfront-known-issues/releases/2022-updates meaning this is something they will fix if they are aware of it.

Best regards,
Ivan

[JohnJOSullivan · Accepted solution]

Nope, just some boneheaded code on my end. I brought it to support and they showed me where the code was off.

That said, I've gone and done some open heart surgery on our major scenarios to replace super-old search modules with the newer ones. They're easier to work with than they were when first released. The old text editor cheat made it not as horrific as I feared.

I'm finally going away on vacation next week and it's been a year since the last time I was on one and I'm way overdue.

-j