Open debnathdubey opened 2 years ago
@dgnorton - this is the OSS version, can your team take a look?
I just discovered/ran into this in cloud2. I lost all my flux for the task I had been working on. It is an unpleasant experience - can we keep the task editor open until the task is validated fully? So if there is an error, the UI stays in the edit mode? The popup error bar doesn't stay around long enough to triage the issue and the flux it refers to is gone too.
I captured a gif
@kristinarobinson - this is an issue in cloud2 as well.
I think this is basically the same issue as https://github.com/influxdata/ui/issues/1444
@kristinarobinson @Luckette team-qx will take this issue. we can discuss more in person next week.
About the bug
Steps to reproduce: List the minimal actions needed to reproduce the behavior.
option task = {name: "No Task", every: 1m, offset: 2s}
slack_endpoint = slack"endpoint" notification = { _notification_rule_id: "08762fc8a72f2000", _notification_rule_name: "My Test Rule", _notification_endpoint_id: "07fd2b39e56ee000", _notification_endpoint_name: "Slack Service", }
from(bucket: "TEST_DB") |> range(start: -1h) |> filter(fn: (r) => r["_measurement"] == "myMeasurement") |> filter(fn: (r) => r["_field"] == "testField") |> aggregateWindow(every: 1m, fn: count, createEmpty: false) |> filter(fn: (r) => r["_value"] > 3) |> monitor["notify"](data: notification, endpoint: slack_endpoint(mapFn: (r) => ({channel: "", text: "Count is getting higher...", color: "danger"})))