Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

1. add nuke slate to the script
2. publish render using local machine rendering
3. publish render with Use existing frames option (will reuse render from previous step)
4. Check the published output. Reviews have correct frame range, but published "main render" is offset one frame. IE if first frame of the shot is 1001 and slate is on frame 1000, published sequence will start with slate on 1001.

Expected Behavior:

Publish should not offset the frame range.

Version

3.17.5

What platform you are running OpenPype on?

Windows

Steps To Reproduce:

see above

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

Removing first collected frame In Validate Rendered frames (L120) solves the issue:

collection.indexes.discard(coll_start)
del repre["files"][0]

[cuID:OP-7358]