fix: fix bad index in compare metadata workflow

[pl]

Important

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Problem

The session field index offset was off by 1 in the compare metadata task causing exceptions.

Changes

Removes the team id from the fields to check, so that the index is correct again.

Does this work well for both Cloud and self-hosted?

N/A

How did you test this code?

Will test on prod.

[greptile-apps]

PR Summary

This PR fixes an index offset issue in the session recording metadata comparison workflow by removing 'team_id' from the FIELD_NAMES list.

• Fixed indexing in compare_recording_metadata_workflow.py by removing 'team_id' from FIELD_NAMES to correctly align with the SQL query results structure
• The code uses FIELD_NAMES.index() + 2 to account for session_id and team_id being at positions 0 and 1 in query results
• This change prevents exceptions when comparing session recording metadata between v1 and v2 storage backends

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}