Javier Molina Sánchez
11/24/2025, 5:04 PMkapa.ai
11/24/2025, 5:04 PMJavier Molina Sánchez
11/25/2025, 9:28 AMkapa.ai
11/25/2025, 9:28 AMkapa.ai
11/25/2025, 9:29 AMsuccess, startedAt, finishedAt, durationInSeconds, etc. [[Webhook payload](https://docs.airbyte.com/platform/1.7/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#configure-webhook-notification-settings)] The knowledge sources you provided do not mention: - Any intentional “batching” or fixed-time emission of notifications (e.g., always at :02 past the hour). - Any change in 1.7.x that would cause notifications to be driven by a cron rather than by job completion time. - Any known 1.7.8-specific bug where some syncs produce notifications and others don’t. The only relevant bug we see is a generic one: “There was a bug with the successful sync webhook code,” which was then fixed, but without version details. [[Webhook issue](https://github.com/airbytehq/airbyte/issues/62117)] It’s unclear from the available sources whether 1.7.8 contains that fix or is affected by some related regression. Because of that, I can’t definitively explain the “always at 802/902pm” behavior or why this morning’s run produced no notification. The documentation simply doesn’t describe any mechanism that would schedule notifications independently of job completion, nor does it give a troubleshooting flow for intermittent notification delivery. Given the limits of the docs/issues you shared, the most I can say confidently is: - Expected behavior (per docs): each successful/failed sync should immediately emit a webhook with the JSON payload shown for “Successful Sync” / “Failed Sync.” [[Webhook payload](https://docs.airbyte.com/platform/1.7/cloud/managing-airbyte-cloud/manage-airbyte-cloud-notifications#configure-webhook-notification-settings)] - Your observed behavior (cron-like times, then no notification) is not described anywhere in these knowledge sources. - There is at least one historical bug around successful sync webhooks, but the sources don’t state whether 1.7.8 is impacted. [[Webhook issue](https://github.com/airbytehq/airbyte/issues/62117)] To go further than this (e.g., confirm if 1.7.8 has a known bug or suggest a concrete patch or config change) would require information that is not present in the documents you provided, so I’d be speculating beyond the available sources.Javier Molina Sánchez
11/25/2025, 9:30 AMkapa.ai
11/25/2025, 9:30 AMkapa.ai
11/25/2025, 9:30 AMmain container: [[Browsing logs](https://docs.airbyte.com/platform/1.7/operator-guides/browsing-output-logs#browsing-on-kubernetes)] bash # Exec into a pod kubectl exec -it <pod-name> -n <namespace> -c main bash # Example from docs: kubectl exec -it destination-bigquery-worker-3607-0-chlle -n jobs -c main bash From the available documentation, I can only say: - You should check logs in the pods that are responsible for running jobs and handling platform functionality, but - The knowledge sources do not specify which exact pod names/components in a 1.7.x deployment are responsible for emitting webhook notifications. So, within the constraints of these docs, I can’t name specific pods beyond “the pod you are interested in” and the example worker pod shown above. [[Browsing logs](https://docs.airbyte.com/platform/1.7/operator-guides/browsing-output-logs#browsing-on-kubernetes)]