Automation to start an application task chain

[rzenere_avvale]

Good morning team,

I want to create an automation to start a task chain.
I've seen that an API endpoint is available on Qlik.dev: Tasks REST | Qlik Developer Portal.
Using a "Raw API Request" block, the configuration seems fine with the definition on Qlik.dev (see below picture)

... but when I run the automation I get a "Request body must be empty" error (see below picture)

Has anyone faced a similar issue?

Riccardo

[eike_s]

Yes, I had the same problem. It works with the block from ‘Qlik Platform Operations’. @Emile_Koslowski are you aware of this problem?

[rzenere_avvale]

Thank you for the tip! We didn't try the 'Qlik Platform Operations' since it should be something in the base Qlik Cloud Services connectors, but we will give it a try.

Riccardo

[marksouzacosta]

Hi @rzenere_avvale ,

It looks like a bug.

I made a workaround adding a string variable, set it to empty and using it in the body request:

Regards,

Mark Costa

[rzenere_avvale]

Thank you for the tip @marksouzacosta! Between the two proposals, I prefer this one since it doesn't need any additional connection.
I'll wait for @Emile_Koslowski or anyone from Qlik Support (i.e. @Daniele_Purrone) to confirm this is a bug or the expected behaviour.

Riccardo

[Daniele_Purrone]

Hi @rzenere_avvale , as this looks like a possible defect, please log a support case mentioning this discussion, and we'll take it further.
Please, provide as much details as possible.

[rzenere_avvale]

Thank you @Daniele_Purrone, I'll go on with a support case and update you as soon as I have any news.

Riccardo

[eike_s]

@rzenere_avvale Completely understandable and makes sense, and I would also prefer this approach in this case. I already had the connection, so it was the quickest solution. Either way, it seems to be a bug, and neither workaround should be necessary.

[rzenere_avvale]

Hi everyone, sorry for the late answer.
Qlik just told me that the issue has been solved and the updated block has been deployed yesterday.
I haven't been able yet to test it, but I'll let you know later in the day.

In case anyone needs the case reference, it is #00409694.

Riccardo

[Daniele_Purrone]

Thanks @rzenere_avvale !

Yes, from our internal testing the issue is now solved. We are waiting for a confirmation from your side 🙂