Hello Everyone,
From the latest major update to 2023.6, I am having issues with some automations and scripts. They were working fine for months with no problems until a few days ago.
Problem is that some automations and scripts issue the following message in traces screen:
running_script: false
limit: 10
I am not sure whether this message appeared before, because some of the automations and scripts reporting such message execute fine with no problems (???), and all actions execute ok. However, some of the automations and scripts are stopping at some point where they did not use to before. One of the automations that are being stop without being executed completely is the following:
alias: Riego
description: ""
trigger:
- platform: time
at: "19:08:00"
enabled: true
- platform: time
at: "04:58:00"
enabled: true
condition: []
action:
- type: turn_on
device_id: cf1684f9f3941edfc7aef516eaa9b2dc
entity_id: switch.lumi_riego_aspersion
domain: switch
- service: timer.start
data:
duration: "0"
data_template:
entity_id: timer.riego_aspersion
duration: "{{ states('input_datetime.riego_aspersion') }}"
- wait_for_trigger:
- platform: state
entity_id: timer.aspersion
to: idle
- type: turn_off
device_id: cf1684f9f3941edfc7aef516eaa9b2dc
entity_id: switch.lumi_riego_aspersion
domain: switch
- delay:
hours: 0
minutes: 0
seconds: 10
milliseconds: 0
- type: turn_on
device_id: cf1684f9f3941edfc7aef516eaa9b2dc
entity_id: switch.lumi_riego_goteo
domain: switch
- service: timer.start
data:
duration: "0"
data_template:
entity_id: timer.riego_goteo
duration: "{{ states('input_datetime.riego_goteo') }}"
- wait_for_trigger:
- platform: state
entity_id: timer.goteo
to: idle
- type: turn_off
device_id: cf1684f9f3941edfc7aef516eaa9b2dc
entity_id: switch.lumi_riego_goteo
domain: switch
mode: single
That’s a simple irrigation automation based on two timers (for two zones) that I can adjust through “input_datetime.riego_aspersion” and “input_datetime.riego_goteo” helpers.
This is the traces screen where the “running_script: false limit: 10” is issued:
And this is the screen where the next step is displayed with some “null” messages are displayed. From that point, automation is not executed:
This is just a sample, as I do have some other automations and scripts with the same problem.
I have seen some similar forum topics but none of them apply to this scenary, but to specific automation problems. I have also realized that most of the problematic automations and scripts (if not all… still checking that) some sort of template is being used at some point of the automation/script. However, I haven’t seen any breaking change for this. Actually, if I execute every step manually one after another, all of them work fine.
Is there any way to increase the “limit:10” value? According to the Scripts documentation, such value can be increased, but it only applies to queued and parallel automations, and this specific automation (and most of them) are single.
Why is this message issued? What does the 10 value mean? Is it a time value, number or parallel threads or any other thing?
Also tried to disable all automations and reanabled as suggested here, but nothing changes in my specific case. Due to this, I am 100% sure that there are not any other automations being executed at the same time.
Is anyone else experiencing the same? Any way to fix this? I have been digging on this for days and I haven’t been able to figure out how to fix it or how to find a workaround.
Thanks in advance!
SĂ©sar