I think it's super important to communicate with your peers... Going on vacation can identify bottlenecks in processes which is actually a good thing.

For instance, it might highlight whether or not your team is too reliant on you to refine every ticket to every level of detail. In my experience, this would be an antipattern that needs solving irrespective of your trip, but your trip might bring it to the forefront.

So using the example above, you could use your trip as an excuse to trial a new way of working for a process that you may otherwise find difficult to try (or not have the confidence to propose, or whatever it might be).

Something I always found useful personally, and advised my team to do, was to list everything they'd be prioritising if they were in work.

Then group items into the things which absolutely must happen, and those which can wait until you get back.

If you're being brutal with prioritisation, communicating effectively, and delegating effectively in your normal day-to-day, you may find that the "must do" list is short (depending on vacation length! :)).

Other things to consider doing:

Make stakeholders aware of who to contact in your absence

Try to not release anything super important while you're off (yes the world won't stop spinning, but just try to release big chunky things before or after your trip)

Ask your team what they need while you're away. What is important to them? What would be a disaster if it happened while you're away?

Took some of the suggestions from https://www.rocketrole.io/ as I left my co-founder recently. It's super useful for last-minute prep, quick upskilling on topics like this, etc. and generally managing your product career to upskill on a regular basis.