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

Warning in Airflow Logs During Sync Operation #22

Open
haarismirza opened this issue Dec 6, 2024 · 1 comment
Open

Warning in Airflow Logs During Sync Operation #22

haarismirza opened this issue Dec 6, 2024 · 1 comment

Comments

@haarismirza
Copy link

I'm encountering a warning in the Airflow logs when running a sync operation using the Hightouch operator. The sync completes successfully, but there is an issue with parsing the output, which triggers a warning. This seems to happen on every sync I've orchestrated through Airflow.

Steps to Reproduce:

  1. Trigger a sync operation using the Hightouch integration in Airflow.
  2. Monitor the Airflow logs during the execution.

Expected Behavior:
The sync operation should complete without warnings, and the output should be parsed correctly without exceptions.

Actual Behavior:
The following warning appears in the Airflow logs:

WARNING - Sync ran successfully but failed to parse output.

The relevant portion of the log is as follows:

[2024-12-06, 19:28:11 UTC] {hightouch.py:99} WARNING - ({'id': 2340695, 'slug': 'REDACTED', ...}, {'id': REDACTED, ...})

Code Snippet:

The following code in the operator is responsible for handling the sync output:

try:
    parsed_result = parse_sync_run_details(
        hightouch_output.sync_run_details
    )
    self.log.info("Sync completed successfully")
    self.log.info(dict(parsed_result))
    return parsed_result.id
except Exception:
    self.log.warning("Sync ran successfully but failed to parse output.")
    self.log.warning(hightouch_output)
@haarismirza
Copy link
Author

@ernestcheng You may be the right person to tag here. Wondering if the issue I opened is correctly captured and if there is any additional information I can provide to get this issue resolved. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant