Multiple service calls stop when one fails

When an automation is setup with multiple services under the action what happens with one of the service calls fails?

.
.
.
action:
  - service: <service_call_1>
    data:
	 <data>
  - service: <service_call_2>
    data:
	 <data>
  - service: <service_call_3>
    data:
	 <data>
  - service: <service_call_n>
    data:
	 <data>

I had an issue where I send a notification to my phone then perform another service call but the notification fail failed (entity_id was wrong) and the whole automation stopped.

This seems like it should not happen or be configurable to proceed to other actions.

Feature request?

Put the service call that can fail into a script.

Within the automation’s action, call the script using this method:

 - service: script.turn_on
   entity_id: script.whatever

The script will be called and the action will continue to the next service call (i.e. it will not wait for the script to finish).

Don’t use this method to call the script because it is designed to wait for the script to finish:

 - service: script.whatever