Automation won't trigger

Configuration
1

Hi all,
I have some integration like the one below that won’t trigger with the time pattern. Manual trigger works, so the condition are met but it seems that they won’t run by time_pattern, I think that the problem could be the multiple trigger:

- alias: "Watchdog camOrtino"
  trigger:
   - platform: state
     entity_id: 'binary_sensor.bi_ortino'
     from: 'on'
     to: 'off'   
     for:
       seconds: 30
        
   - platform: time_pattern
     minutes: "/5"
      
  condition:
   - condition: and
     conditions:
      - condition: state
        entity_id: 'script.attesa_ortino'
        state: 'off'
      - condition: state
        entity_id: 'input_boolean.e_mode'
        state: 'off'
      - condition: state
        entity_id: 'binary_sensor.bi_ortino'
        state: 'off'
      - condition: not
        conditions:
         - condition: state
           entity_id: sensor.wifi_ortino
           state: 'unavailable'
        

  action:
    - service: homeassistant.turn_on
      entity_id: 'switch.esp_ortino'
    #- service: script.reload_esportino
    - service: homeassistant.turn_on
      entity_id: 'script.attesa_ortino'
    - delay: '00:00:15'
    - service: homeassistant.turn_off
      entity_id: 'switch.esp_ortino'

Thanks for any suggestion

2

If you manually trigger thevautonation the cknditions are skipped so it could still be the conditiobs causing the failure.

Look at the automation trace to see why it isn’t working.

3

Do scripts have an on/off state?

4

Solved, one condition was bad.
Yes, scripts are in “state” ON when running (in My case is used to have a common timer that won’t allow multiple trigger).
To check where the automation was going wrong i’ve added the ID to the automation and then checked the runtime from Lovelace.

- alias: "Watchdog camOrtino"
  id: '78373823988'
  trigger: