[🐛 Bug]: Unclear error for python step execution

[woelfel-tn]

Describe the bug
I have following workflow:

workflow: id: provider-alias name: Derive providerAlias from Keep providers description: Lookup display_name for alert.providerId via Keep API; fallback to "unknown". disabled: false triggers: - type: alert filters: [] inputs: [] consts: {} owners: [] services: [] steps: - name: get-providers provider: type: http config: "{{ providers.default-http }}" with: url: http://keep.internal/providers method: GET headers: X-API-KEY: "{{ secrets.keepApiKeyReal }}" - name: pick-display-name provider: type: python config: "{{ providers.default-python }}" with: code: | data = {{ steps.get-providers.results}} | tojson pid = '{{alert.providerId}}' name = '' for p in (data.get('providers', []) if isinstance(data, dict) else []): if str(p.get('type', '')) == pid: name = p.get('display_name') or '' break {'display_name': name} actions: - name: set-provider-alias if: "'{{ steps.pick-display-name.results.display_name }}' != ''" provider: type: mock config: "{{ providers.default-mock }}" with: enrich_alert: - key: providerAlias value: "{{ steps.pick-display-name.results.display_name }}" - name: set-unknown if: "'{{ steps.pick-display-name.results.display_name }}' == ''" provider: type: mock config: "{{ providers.default-mock }}" with: enrich_alert: - key: providerAlias value: unknown

And get the following unclear error in workflow execution details:

Got SyntaxError while parsing token 'keep.kb.us-central1.gcp.cloud.es.io', 'validation': 'any_http_url', 'default': None}, 'kibana_port': {'required': False, 'description': 'Kibana Port (...)': invalid syntax (<unknown>, line 1)

To Reproduce
Steps to reproduce the behavior:

1. Create a the workflow
2. Try to execute it on an alert
3. Get the unclear error message

Expected behavior
A clear error what the problem with the python code is.

[dosubot]

The unclear error message you’re seeing is due to how the Python provider in Keep handles exceptions: it catches errors (including SyntaxError) during code execution and wraps them in a generic ProviderException, which can result in messages that are hard to interpret or don’t pinpoint the exact problem in your Python code. The error reporting currently doesn’t sanitize or clarify syntax errors, so details like the problematic token or line number may be buried or formatted poorly in the output. Improving this is possible in the provider’s code, but there haven’t been recent changes specifically targeting clearer Python error messages yet (source).

For now, double-check your Python code for syntax issues, especially around how template variables are rendered and how data is passed between steps. If you’re using test runs, be aware of a known bug where code strings can be parsed incorrectly as YAML, causing misleading errors—this was fixed in PR #5031, so make sure you’re on a recent version if you hit that scenario (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}