Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automation "call-webhook" action does not render correct "work_pool" data #15668

Open
EmilRex opened this issue Oct 11, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@EmilRex
Copy link
Contributor

EmilRex commented Oct 11, 2024

Bug summary

  1. Create a webhook block pointing to somewhere you can see the incoming calls (I used https://webhook.site/)
  2. Create an automation that triggers based on Work pool status with a call-webhook action that uses your webhook block
  3. Leave the default body:
{
  "message": "Name: {{ work_pool.name }}\nStatus: {{ work_pool.status }}\nURL: {{ work_pool|ui_url }}"
}
  1. Trigger the automation
  2. Observe that the values are none:
{
  "message": "Name: \nStatus: \nURL: None"
}

Doing the same thing with a notification action does render the correct "work_pool" data.

Version info (prefect version output)

Cloud - N/A

Additional context

No response

@EmilRex EmilRex added the bug Something isn't working label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant