Hi @maddan80 

Thank you for reaching out with your question and providing the context about your use case.

Per your comments, having a 200 Status Code in Serverless is a good initial indicator that the request is reaching the Oracle UCM server. Brainstorming... the problem could be in how the response is handled in a different environment (Serverless)

There are Serverless environment versions with different configurations of Python, Scala, and the JDK. Use a version that matches the configuration used in your all-purpose and job clusters.

BTW, in Lakeflow Jobs, you can configure an environment for each of your job tasks where you can select a specific Version and dependencies

Other considerations: 

• Check for any Serverless limitations 
• Do you have a unit test that can validate a simple call (such as a health check) before requesting data? This could help determine whether the issue is general or specific to your search, such as Serverless being unable to reach the Oracle UCM host.
• Is the "manifest_file_prefix" variable checked for encoding as well? This could potentially mess with the query_text variable and/or affect the results.
• Even with a 200 Status, look further in the SOAP body's response and explicitly check for expected nodes.

I hope this helps! 
Thank you