fix(source-snapchat-marketing): "Start time should start at the beginning of an hour" error

[ali-taha-ahmed]

What

Fixes the timestamp formatting for start_datetime and end_datetime to ensure compatibility with Snapchat's API, which requires times to start exactly at the beginning of the hour.
Resolves: #61499

How

For daily streams, set datetime format to:

%Y-%m-%dT%H:00:00
to ensure times always start at the top of the hour.

For hourly streams, set datetime format to:

%Y-%m-%dT%H:00:00.000000%z
to match Snapchat’s expected precision and timezone formatting.
These formats fix invalid start/end time errors from the API and align partitioning with Airbyte’s incremental sync logic.

Review guide

User Impact

✔ No more 400 errors due to improperly formatted timestamps

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[vercel]

@ali-taha-ahmed is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

👋 Welcome to Airbyte!

Thank you for your contribution from ali-taha-ahmed/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

• PR Guidelines: Check our guidelines for contributions.
• Developing Connectors Locally: Learn how to set up your environment and develop connectors locally.
• If you enable BYO Connector Credentials within your fork, you can view your test results here:
  

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

• /format-fix - Fixes most formatting issues.
• /bump-version - Bumps connector versions.
• /run-connector-tests - Runs connector tests.
• /run-cat-tests - Runs CAT tests.
• /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

1. "Vercel" CI failures. You can always ignore these. These are our docs builds but they can only be run by approval. A maintainer will approve the workflow upon request, but this failure should not be of concern.
2. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
   • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
3. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
4. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

[ali-taha-ahmed]

/format-fix

[ali-taha-ahmed]

/bump-version changelog="Fix Start time should start at the beginning of an hour error"

[marcosmarxm]

@tolik0 @darynaishchenko can you check this contribution as you made a fix to datetime in current version?

[cgardens]

note to self: referred to internal team -- extensibility

[tolik0]

/bump-version changelog="Fix start time for stats streams"

Bump Version job started... Check job output.

✅ Changes applied successfully. (3feec79)

[tolik0]

/format-fix

Format-fix job started... Check job output.

🟦 Job completed successfully (no changes).

[tolik0]

/run-cat-tests

Connector CAT tests started... Check job output.

If the connector supports live tests or regression tests, you may want to run those now also:

• Run Live Tests
• Run Regression Tests

CAT Tests completed.
Important: Please check the job output to verify the results.

[tolik0]

Tests are in this PR: #64551

[katmarkham]

Anatolii validated this on his branch!