I have created an eloqua cloud app with an action service.
To test it, I am creating a multi-step campaign which is really simple:
A segment with a couple of members flows into my action cloud service, which then flows into something else like an email or something.
However, I am having trouble getting the contacts to flow through the cloud service action step: they all seem to be stuck there and are not continuing.
According to both the Bulk 2.0 api documentation and the sites on making an action service (Develop an AppCloud Action Service),
when contacts flow into the action service step, eloqua will request out to my notification url (I am getting this successfully),
after that, I am to respond with some status code, and the example is a 204 status code followed by an asynchronous bulk data import/export.
My action doesn't require any import or export, and my goal is to either do my work and respond back that I am finished, or if it will take some time: respond back to have eloqua wait, then send a request later that I am finished.
After this, the contacts can flow on to the next step in the campaign canvas.
So, I realize that after I get the notification I can respond with a 204 status to let eloqua know that I will use the bulk api's async calls to import/export data.
But what other statuses can I use if I don't want to or don't need to use the async api calls?
Can I just return a 200 status if I am done and want eloqua to proceed to the next campaign step?
Can I return some status to make eloqua wait for me to do some processing on my side, followed by some status to let eloqua proceed?
I have tried several different 200 level statuses and none of them seem to let my contacts move on to the next step.
Please help.
thanks,
Chris