EM API Error Response For Compose Failure

NewbieQlik — Fri, 14 Mar 2025 20:49:07 GMT

We are using AWS lambda to trigger a compose job using Qlik EM API's and we have automated the whole orchestration using a step function. The first step in the process is trigger the compose wf and once the job is triggered, the next step will check the compose wf status using get_task_details by passing server name and wf name.

The compose wf failed during the execution with this error "Terminated: sqlstate 42S02, errorcode 2003, message SQL compilation error:Object does not exist or not authorized. Cause: " but the response that we received from EM API is entirely different. The error message that I am getting is "There is no error port defined for failed node.". I also observed that when it fails it retries 3 time and at the end it is failing with this error.

Any help on this topic is greatly appreciated.

This is how I am invoking get_task_details from my lambda

status= aem_program.aem_client.get_task_details(server.name,wfname)

server.name:- name of the server where I have to run the compose wf using EM API

wfname:- <Workflowname>__<Project Name> I am sending the wf name in this format

print("message",status.message) :- This is how I am getting the error message

Re: EM API Error Response For Compose Failure

sureshkumar — Thu, 23 May 2024 10:29:09 GMT

Hello @NewbieQlik

To get better insight of the issue, i would suggest you open a support ticket.

Note: This kind of automation process are best handled by our Professional Service Team.

Regards,

Suresh

topic EM API Error Response For Compose Failure in Qlik Compose

EM API Error Response For Compose Failure

Re: EM API Error Response For Compose Failure