Hello guys, I need your help with correct errors handling. Log example:

'event': "General exception [muted]: () The given API key doesn't match service's internal, primary or secondary keys.", 'run_id': '019cc39a-6210-791a-8621-cd41b681b61e', 'level': 'info', 'timestamp': '2026-03-06T14:43:31.690462Z'}: source="airflow.providers.cncf.kubernetes.utils.pod_manager.PodManager"

As you can see I ran Meltano pipeline inside Airflow. Exception was raised during the run. But

log_level

says that it's only

info

and I see

[muted]

prefix before the log, which makes me think that I configured something incorrectly and Meltano continues to run regardless of the error that occurred. I want to re-raise exceptions during pipeline run, so I can see that my run has some issues inside and I should fix them. Maybe some kind of

exit_code=1

? Currently my runs are marked as successful but in fact - they're not. Thanks in advance 🙏 Best regards, Alex

Hi Alex, This might be a useful thread to read on the

info

log level as surfaced by Meltano: https://meltano.slack.com/archives/C068YBQQF1V/p1770741803189799 It may also be that the tap/API is doing something funky - I have never seen

[muted]

output by Meltano before... Some more context on the command you are running/plugins you are using would be helpful.

Thanks for response! Yea, I can provide some info about my plugins. Such logs are generated by Azure Search / Azure Blob inside my Meltano Target. Command that I used is:

meltano run <tap_name> azure_target

Nothing special, no options / params.

I have never seen [muted] output by Meltano before

-> that's sad. I thought I just missed some config var so my exceptions are muted by Meltano.

Is the tap or target a custom one or something on the Hub? I believe

The given API key doesn't match service's internal, primary or secondary keys.

is a common response from Azure's API.