Bug: Tray Publisher Editorial fails on validating asset frame range due to asset nog existing yet

[BigRoy]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

When publishing via Tray Publisher Editorial to new assets it errors with the This is not your fault error.

Here's the zipped log:
publish-report-231006-11-21_fail_on_asset_entity.zip

Which shows error:

It's a KeyError on instance.data["assetEntity"] because the asset document does not exist in the database yet and thus has not been collected accordingly.

Expected Behavior:

I suppose for this type of publish where the tray editorial "decides" on the shots frame range the validation for frame range should not occur at all?

Version

3.17.2-nightly.3

What platform you are running OpenPype on?

Windows

Steps To Reproduce:

1. Publish Editorial via TrayPublisher to new non-existing assets

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:

Originally reported on Discord.

[cuID:OP-7091]

[BigRoy]

Not entirely sure but I suspect this is still an issue in ayon but with folderEntity?
@LiborBatek can you confirm?

[LiborBatek]

@jakubjezek001 speaking of working with Editorial is more suited for this kind of decision/testing ??