Telegraf crushed if one of many outputs unavailable

Hello!
We are using telegraf 1.14.5 with influx and elastic and faced a problem, when one of them is unavailable then telegraf crushes and don’t sending anything to both of that systems. Is there any possibilities to configure telegraf that way, that it doesn’t will be crushed?
Our current config

telegraf.conf:
----
[global_tags]
  env = "$HOSTNAME"
  ip = "$HOSTIP"
  pod = "$PODNAME"
  service = "$SERVICENAME"
[agent]
  collection_jitter = "0s"
  debug = true
  flush_interval = "10s"
  flush_jitter = "0s"
  hostname = "$HOSTNAME"
  interval = "10s"
  logfile = ""
  metric_batch_size = 1000
  metric_buffer_limit = 10000
  omit_hostname = false
  precision = ""
  quiet = false
  round_interval = true


[[outputs.influxdb_v2]]
  bucket = "$INFLUXBUCKET"
  organization = "organization"
  timeout = "5s"
  token = "$INFLUXTOKEN"
  urls = [
    "$INFLUXHOST"
  ]
[[outputs.elasticsearch]]
  health_check_interval = "10s"
  index_name = "telegraf-%Y.%m.%d"
  manage_template = true
  password = "$ELASTICSEARCH_PASSWORD"
  template_name = "telegraf"
  timeout = "5s"
  urls = [
    "http://$ELASTICSEARCH_URL"
  ]
  username = "$ELASTICSEARCH_USER"