25356943 CustomerApi.Jobs.PublishNotificationJob
Queue notifications
Attempt 5 of 5
Priority 0
Tags ...
Node customer_api@10.10.1.109
Queue Time 00:00.295
Run Time 00:00.010
Inserted 2h ago
Scheduled 2h ago
Completed
Cancelled
Discarded 2h ago

Args

%{
  "account_id" => "107777",
  "data" => %{
    "account_insight_agent_id" => "a34152b0-64d1-470a-9a23-2927bf24bf1f",
    "insights" => [
      %{
        "action_plan" => "Update the phrase to **\"as well within the Replicas column\"**. This is a low-risk copy fix in a live flow and should improve polish immediately.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web_builder update_step_content tool to update the published web flow with ID 5b20fa72-f487-4418-849e-becb4b8d7025. In step eeff8bdd-f8c9-4e7d-b49f-144ffe02def6, hotspot cca8c5e6-05f5-41bc-ab4f-b5637a7a58dc, replace the body copy phrase \"as well with in the Replicas column\" with \"as well within the Replicas column\". Do not change any other copy.",
            "title" => "Fix typo in Kubernetes cluster flow",
            "undo_prompt" => "Use the web_builder update_step_content tool to update the web flow with ID 5b20fa72-f487-4418-849e-becb4b8d7025. In step eeff8bdd-f8c9-4e7d-b49f-144ffe02def6, hotspot cca8c5e6-05f5-41bc-ab4f-b5637a7a58dc, change the phrase \"as well within the Replicas column\" back to \"as well with in the Replicas column\"."
          }
        ],
        "cta_text" => "Review typo",
        "entity_id" => "5b20fa72-f487-4418-849e-becb4b8d7025",
        "entity_type" => "flow",
        "expected_impact" => "Removes a visible spelling issue in a live onboarding flow, improving trust and perceived product quality.",
        "finding" => "In **Kubernetes cluster**, the live copy includes the phrase **\"as well with in the Replicas column\"**, where **\"with in\"** appears to be an English typo for **\"within\"**.\n\nReview it here: [Kubernetes cluster](https://studio.appcues.com/flows/5b20fa72-f487-4418-849e-becb4b8d7025/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "Live Kubernetes cluster flow has a visible typo",
        "type" => "issue"
      },
      %{
        "action_plan" => "Correct the terminology to **\"Bake agent package\"** and simplify the instruction sentence to something clearer, such as **\"Click 'Bake agents' to bake a new agent package.\"** Because this flow is instructional, even small copy errors can create confusion.",
        "actions" => [
          %{
            "cta" => "Run",
            "prompt" => "Use the web_builder update_step_content tool to update the published web flow with ID ffb9fa7b-ee4c-4386-b1af-3bc78b47a3f9. Make these exact copy corrections only: 1) In step 9312f8fb-de2e-40ac-9e5c-d05590f2d424, change the bullet text \"Set “Back agent package” to “Back a specific agent package for this folder”\" to \"Set “Bake agent package” to “Bake a specific agent package for this folder”\". 2) In step 0cea369d-e395-4be5-93f0-b9b54f9bf252, replace the sentence \"Click on \\\"Bake agents\\\" for baking agents. and bake yourself a new agent.\" with \"Click \\\"Bake agents\\\" to bake a new agent package.\" Do not change any other text.",
            "title" => "Fix typos in Agent Setup flow",
            "undo_prompt" => "Use the web_builder update_step_content tool to update the web flow with ID ffb9fa7b-ee4c-4386-b1af-3bc78b47a3f9. Revert these exact copy changes: 1) In step 9312f8fb-de2e-40ac-9e5c-d05590f2d424, change \"Set “Bake agent package” to “Bake a specific agent package for this folder”\" back to \"Set “Back agent package” to “Back a specific agent package for this folder”\". 2) In step 0cea369d-e395-4be5-93f0-b9b54f9bf252, change \"Click \\\"Bake agents\\\" to bake a new agent package.\" back to \"Click on \\\"Bake agents\\\" for baking agents. and bake yourself a new agent.\""
          }
        ],
        "cta_text" => "Review typos",
        "entity_id" => "ffb9fa7b-ee4c-4386-b1af-3bc78b47a3f9",
        "entity_type" => "flow",
        "expected_impact" => "Cleaner instructions should reduce friction in a setup flow and improve confidence during agent configuration.",
        "finding" => "In **Checkmk SaaS - Agent Setup**, I found multiple likely English typos in live copy:\n\n- **\"Back agent package\"** appears to be intended as **\"Bake agent package\"**\n- **\"Click on \\\"Bake agents\\\" for baking agents. and bake yourself a new agent.\"** contains awkward/incorrect phrasing and sentence punctuation\n\nReview it here: [Checkmk SaaS - Agent Setup](https://studio.appcues.com/flows/ffb9fa7b-ee4c-4386-b1af-3bc78b47a3f9/analytics)",
        "outcomes" => ["activation", "engagement"],
        "priority" => "high",
        "title" => "Agent Setup flow contains multiple likely copy typos",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "2a28b618-ae95-4e95-bcf0-6deabde4aed6",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

Attempt 5—2h ago

** (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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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

Attempt 4—2h ago

** (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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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

Attempt 3—2h ago

** (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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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

Attempt 2—2h ago

** (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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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

Attempt 1—2h ago

** (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+dd24b211) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+dd24b211) 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