Args

%{
  "account_id" => "33213",
  "data" => %{
    "account_insight_agent_id" => "17ad42ca-3bb7-4488-b407-6f3b0e223270",
    "insights" => [
      %{
        "action_plan" => "Update the heading to match the product term used in the rest of the message. The safest correction is **\"Locations with SOV\"** so the heading aligns with the renamed schedule and reduces confusion for brokers reviewing property location schedules.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web experience content update tool to update the published web flow named \"New Commercial Property Locations SOV | PDL - 473\" (experience ID: fdbfd868-8ba3-4ffd-8dda-3d843af6fbce). In the published modal step, change the heading text from exactly \"Location with SOV Schedule\" to exactly \"Locations with SOV\". Do not change any other copy or settings. After updating, publish the change if required to make the corrected copy live.",
            "title" => "Fix heading in SOV update flow",
            "undo_prompt" => "Use the web experience content update tool to update the published web flow named \"New Commercial Property Locations SOV | PDL - 473\" (experience ID: fdbfd868-8ba3-4ffd-8dda-3d843af6fbce). In the published modal step, change the heading text from exactly \"Locations with SOV\" back to exactly \"Location with SOV Schedule\". Do not change any other copy or settings. After updating, publish the change if required to restore the previous live copy."
          }
        ],
        "cta_text" => "Review typo",
        "entity_id" => "fdbfd868-8ba3-4ffd-8dda-3d843af6fbce",
        "entity_type" => "flow",
        "expected_impact" => "Cleaner release messaging and less confusion around the renamed schedule, improving comprehension of this workflow update.",
        "finding" => "In **[New Commercial Property Locations SOV | PDL - 473](https://studio.appcues.com/flows/fdbfd868-8ba3-4ffd-8dda-3d843af6fbce/analytics)**, the live heading reads **\"Location with SOV Schedule\"**.\n\nThat appears inconsistent with the body copy, which says the schedule name changed to **\"Locations with SOV\"** and refers to **\"Location schedules\"** in the plural. The heading is likely missing the plural **s** and may be using the old phrasing.",
        "outcomes" => ["engagement", "adoption"],
        "priority" => "medium",
        "title" => "Published release announcement likely has a singular/plural typo",
        "type" => "issue"
      },
      %{
        "action_plan" => "Rename the experience to **\"Submission Details Report\"** so the Studio title matches the live heading. This will make the flow easier for your team to find and maintain, and it removes a likely typo from the experience title.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web experience update tool to rename the published web flow with experience ID 68e8c48a-5ce7-44f0-9cb6-a96172a71d50. Change the experience name from exactly \"Submissions Details List Report\" to exactly \"Submission Details Report\". Do not modify step content, rules, or targeting. If publishing is required for the renamed title to be reflected in Studio, publish only after the rename is applied.",
            "title" => "Rename submission report flow",
            "undo_prompt" => "Use the web experience update tool to rename the published web flow with experience ID 68e8c48a-5ce7-44f0-9cb6-a96172a71d50. Change the experience name from exactly \"Submission Details Report\" back to exactly \"Submissions Details List Report\". Do not modify step content, rules, or targeting. If publishing is required for the reverted title to be reflected in Studio, publish only after the rename is applied."
          }
        ],
        "cta_text" => "Review title typo",
        "entity_id" => "68e8c48a-5ce7-44f0-9cb6-a96172a71d50",
        "entity_type" => "flow",
        "expected_impact" => "Better internal clarity for the Appcues team and more consistent naming between the experience title and the live copy.",
        "finding" => "The live flow **[Submissions Details List Report](https://studio.appcues.com/flows/68e8c48a-5ce7-44f0-9cb6-a96172a71d50/analytics)** appears to have a naming typo.\n\nThe experience name uses **\"Submissions Details\"**, while the in-flow heading shown to users is **\"Submission Details Report\"**. The singular form in the live copy reads more naturally and is likely the intended wording.",
        "outcomes" => ["engagement"],
        "priority" => "low",
        "title" => "One live flow name appears to contain a title typo",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "877d5efc-166e-4823-a05f-b3ccee4e0499",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1776798994316736, "structured" => true}

Errors

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4

** (Knock.ApiKeyMissingError)   The api_key setting is required to make requests to Knock.
  Please configure :api_key in config.exs, set the KNOCK_API_KEY
  environment variable, or pass into a new client instance.

    (knock 0.5.0) lib/knock/client.ex:65: Knock.Client.new/1
    (customer_api 1.21.0+a640f45e) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+a640f45e) lib/customer_api/jobs/publish_notification_job.ex:93: CustomerApi.Jobs.PublishNotificationJob.do_publish/4
    (oban_pro 1.6.12) lib/oban/pro/worker.ex:1156: Oban.Pro.Worker.process/3
    (oban 2.20.3) lib/oban/queue/executor.ex:145: Oban.Queue.Executor.perform/1
    (oban 2.20.3) lib/oban/queue/executor.ex:77: Oban.Queue.Executor.call/1
    (elixir 1.19.5) lib/task/supervised.ex:105: Task.Supervised.invoke_mfa/2
    (elixir 1.19.5) lib/task/supervised.ex:40: Task.Supervised.reply/4