Remember the compatibility of certain snaps for Ultra pipelines. Aggregate
and certain snaps will not work with Ultra configurations. Do you have any
of them?
You cannot just straight away convert from Triggered to Ultra. It just wont
work as is. You will have to consider retesting and converting certain
snaps.
Thanks & Regards,
Naveen
@nganapathiraju thanks for your message. Maybe my question was a bit unclear. My pipeline runs successfully both as a triggered task and as an Ultra task. The problem is that it appears that the return payload for Ultra is different from a regular triggered task. I have not been able to find documentation that clearly specifies if or how the return payload for a pipeline (functioning correctly under ultra) is different as a triggered task vs an ultra task. The behavior of my pipeline strongly suggests that that is the case. I was hoping for some assistance in identifying how the return value of an ultra pipeline is different.
Omair
Review this
Maybe that will help. Definitely the return from Ultra is different from
Triggered in the sense that content is also json encoded depending on how
you handle in your mapper.
Thanks & Regards,
Naveen
