Problem with next_alarm and snooze

I’m struggling to create an automation for my morning routine that uses the next_alarm sensor from my phone. The issue I’m having is that I use the sensor as my trigger, but if I hit snooze - which I do often and usually within a few seconds of the alarm going off - it over-writes the value of the next_alarm sensor and the automation errors out. Does anyone have a solution for a better trigger that will use my original morning alarm and not get over-written by the snooze?

Note - I’ve tried changing the mode of the automation from single, to parallel, to queued, but none of those helped. Also, I’ve used the automation with a different trigger and it works fine.

Here is the automation:

alias: "SCHEDULE: Morning Routine when phone alarm goes off "
description: ""
trigger:
  - platform: time
    at: sensor.alex_phone_next_alarm
condition:
  - condition: state
    entity_id: input_boolean.vacation_mode
    state: "off"
  - condition: time
    before: "00:00:00"
    weekday:
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
      - sun
    after: "06:10:00"
action:
  - delay:
      hours: 0
      minutes: 10
      seconds: 0
      milliseconds: 0
  - service: script.schedule_morning_wake_up
    data: {}
mode: parallel
max: 10

The script kicks off a few service calls: (1) open blinds (2) play radio station on bedroom speaker

Maybe use a wait time after it has been triggered?

maybe try mode: restart ?

if not then I would look into checking that the server time is in sync with phone etc…

Turns out the issue was actually with my script. The script was working fine during testing and somehow overnight, the service call within the script no longer works. The integration of the cover stopped working and therefore the script wouldn’t run. Anyway, thanks for trying to help!