What is `resolved-props` in remotion-lambda bucket and can it's items be expired?

[languid kindle]

Remotion 4.0.167

The remotion-lambda bucket seems to have a resolved-props folder containing json files of the inputProps after they have gone through calculateMetadata(). We augment inputProps in calculateMetadata() and we can see the augmentation in the json files.

We can't find any documentation on this in remotion lambda. Wondering what problem this folder solves. Also, can we put an s3 lifecycle rule on its contents to expire the json files and what would be the recommended expiration time?

[crystal sapphire]

I believe it's acting as a cache across your rendering cycle so it only needs to resolve once. I don't see any issue expiring these if the task has completed -- but I am no expert here.

[vague flax]

hi @languid kindle!

this is a workaround for the fact that a lambda function can only have a invocation payload smaller than 64KB.
you have resolved props (https://www.remotion.dev/docs/props-resolution) that are bigger than that so we save them to S3 and then fetch them from inside the lambda function

those should be deleted automatically actually!
I will check if that logic is still working correctly - maybe those are leftovers from failed renders?