Test JSON Parameters missleading or not working properly scheduled trigger

💬 Workflows
1

This behaviour is misleading and probably wrong: If I add a value on the trigger Test JSON Parameters it should be ignored by a scheduled workflow run because it is supposed to be used only when a workflow is tested so is a manual run. So or it is a bug or it is misleading the Title of that box

onPrem: 3.196.2

I didn't test the Test Header Params I would review that one too.

Cheers

image
image376×320 14.9 KB

image
image762×126 17.2 KB

3

Hi @dda,

Apologies for this issue and thank you for reporting!

It looks like a bug report has been created by the amazing Blake Reed and sent to the workflows engineering team. I can update this post with any news I hear on the ticket :saluting_face:

4

Was bit by this today as well. Any chance there is upcoming progress here?

5

Hey @lkiss - there's been a fair bit of internal chatter and planning about this particular issue, but no concrete action just yet. It's definitely on our roadmap, though.

While not ideal, one foolproof way to programmatically distinguish between scheduled and manual runs is to reference workflowContext.triggerType. This will evaluate to webhook, cron, or manual.

6

one foolproof way to programmatically distinguish between scheduled and manual runs is to reference workflowContext.triggerType. This will evaluate to webhook, cron, or manual.

That’s great. Thanks for the quick tip.

1 Like