v1.1.14

Fixes

• Vacation flows no longer mis-target the weekly schedule flow. When setting up a cloud vacation, the Start/End flows resolve the weekly schedule flow's runtime id so they can pause it at vacation start and resume it at vacation end. A shared flow-id cache (PowerAutomate.Flow.*) could be left holding a vacation flow's identity, because it is re-read right after import. The fallback resolver trusted that cache without verifying its display name, so when the live weekly lookup missed, the End flow turned the vacation Start flow back on at vacation end instead of the weekly schedule flow. Result: the weekly schedule never resumed, and the Start flow's one-shot trigger re-fired (Power Automate ignores count:1 and re-fires a past-start recurrence on enable). The resolver now only adopts the cached environment + flow id when the cached display name matches the weekly flow.

Note: already-imported vacation flows still carry the old (wrong) target. Re-run Set up vacation in cloud to regenerate them with the corrected pause/resume target.