Skip to content

[Proofpoint TAP] Clarify state restoration log to “last ingestion run attempt”#6493

Closed
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-log-message-ingestion-attempt
Closed

[Proofpoint TAP] Clarify state restoration log to “last ingestion run attempt”#6493
Copilot wants to merge 2 commits into
masterfrom
copilot/fix-log-message-ingestion-attempt

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 21, 2026

The Proofpoint TAP connector logs last_campaign_datetime as “last ingested,” which is misleading because the value represents the timestamp from the previous ingestion run attempt. This update aligns log wording with actual connector behavior.

  • Log semantics

    • Updated connector INFO log in state restoration path from:
      • Connector last ingested {state_key} datetime
    • to:
      • Connector last ingestion run attempt {state_key}
  • Regression coverage

    • Added a focused unit test asserting _initiate_work() emits the updated message with last_campaign_datetime metadata when state is present.
self._logger.info(
    f"[CONNECTOR] Connector last ingestion run attempt {state_key}",
    {state_key: last_ingested_datetime_str},
)

Copilot AI changed the title [WIP] Fix misleading log message about last ingestion run attempt [Proofpoint TAP] Clarify state restoration log to “last ingestion run attempt” May 21, 2026
Copilot AI requested a review from SamuelHassine May 21, 2026 21:45
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

Successfully merging this pull request may close these issues.

[Proofpoint TAP] - Log about last attempt is misleading

2 participants