25115136 CustomerApi.Jobs.PublishNotificationJob
Queue notifications
Attempt 5 of 5
Priority 0
Tags ...
Node customer_api@10.10.0.159
Queue Time 00:00.348
Run Time 00:00.007
Inserted 9h ago
Scheduled 9h ago
Completed
Cancelled
Discarded 9h ago

Args

%{
  "account_id" => "120584",
  "data" => %{
    "account_insight_agent_id" => "c43e9ff4-8b6b-432a-8a4a-f2ccf16e824e",
    "insights" => [
      %{
        "action_plan" => "Update the banner copy to restore the missing spaces after the periods. After publishing the corrected banner text, re-check the full sentence once in Studio to make sure no other punctuation spacing was introduced.",
        "actions" => [],
        "cta_text" => "Review banner copy",
        "entity_id" => "03256f9d-75b9-41d0-a5e8-dc1be449f11e",
        "entity_type" => "banner",
        "expected_impact" => "Cleaner production-facing communication and fewer trust-eroding copy errors in a high-visibility live banner.",
        "finding" => "In **CNN Production restructure**, the live banner copy still contains two punctuation-spacing errors in the same sentence.\n\nExperience: [CNN Production restructure](https://studio.appcues.com/banners/03256f9d-75b9-41d0-a5e8-dc1be449f11e/analytics)\n\nPossible typos:\n- `10pm ET.Please` → likely `10pm ET. Please`\n- `data loss.With` → likely `data loss. With`\n\nThis is a live banner, so the issue is user-visible on every display.",
        "outcomes" => ["engagement"],
        "priority" => "high",
        "title" => "CNN restructure banner still has broken sentence spacing",
        "type" => "issue"
      },
      %{
        "action_plan" => "Edit the body sentence so the plural noun and verb agree. Once updated, preview the flow to verify the rewritten line still fits the layout cleanly.",
        "actions" => [],
        "cta_text" => "Review flow copy",
        "entity_id" => "4f111f15-ea63-4604-810c-d45408d5d4f5",
        "entity_type" => "flow",
        "expected_impact" => "Improves message credibility for a promotional flow and reduces friction in a key upgrade prompt.",
        "finding" => "The live flow **Webinar entry point - audience 1+2 (onboarding intent or clicking hooks)** includes a likely grammar typo in its main value statement.\n\nExperience: [Webinar entry point flow](https://studio.appcues.com/flows/4f111f15-ea63-4604-810c-d45408d5d4f5/analytics)\n\nPossible typo:\n- `live webinars that drives real engagement` → likely `live webinars that drive real engagement`\n\nBecause this line sits in the primary body copy, it weakens the polish of the upgrade message.",
        "outcomes" => ["conversion", "engagement"],
        "priority" => "medium",
        "title" => "Webinar entry flow has a subject-verb agreement error",
        "type" => "issue"
      },
      %{
        "action_plan" => "Update that sentence in the What’s New modal and scan the surrounding section for similarly compressed phrasing before republishing.",
        "actions" => [],
        "cta_text" => "Review release-note copy",
        "entity_id" => "ed708631-6e40-462c-8ff8-e1ce0a7ade87",
        "entity_type" => "flow",
        "expected_impact" => "Makes a high-traffic release-note experience read more naturally and reinforces product polish.",
        "finding" => "In the live **What's new - One scrollable popup on the center** flow, one sentence appears to be missing an article.\n\nExperience: [What’s New flow](https://studio.appcues.com/flows/ed708631-6e40-462c-8ff8-e1ce0a7ade87/analytics)\n\nPossible typo:\n- `ready to edit or turn into clip` → likely `ready to edit or turn into a clip`\n\nThe rest of the flow copy reads naturally, so this phrase stands out as an avoidable copy slip.",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "What’s New flow includes a likely missing article",
        "type" => "issue"
      },
      %{
        "action_plan" => "Revise the banner sentence to include the missing article, then quickly review the rest of the banner for clarity since finance notices are especially sensitive.",
        "actions" => [],
        "cta_text" => "Review finance banner",
        "entity_id" => "880f0c9f-8715-4bad-979e-46f83ab5beb2",
        "entity_type" => "banner",
        "expected_impact" => "Improves clarity and trust in a billing-related alert that may prompt urgent customer action.",
        "finding" => "The live **Finance announcement** banner contains a likely article omission.\n\nExperience: [Finance announcement](https://studio.appcues.com/banners/880f0c9f-8715-4bad-979e-46f83ab5beb2/analytics)\n\nPossible typo:\n- `You have missing invoice` → likely `You have a missing invoice`\n\nThis reads as ungrammatical in English and may make a billing-related notice feel less trustworthy.",
        "outcomes" => ["engagement", "retention"],
        "priority" => "medium",
        "title" => "Finance announcement banner has an article omission",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "d0cf75d5-6607-415a-9090-9dcac3adad3e",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

Attempt 5—9h 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+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) 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—9h 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+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) 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—9h 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+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) 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—9h 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+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) 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—9h 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+88574494) lib/customer_api/services/knock.ex:65: CustomerApi.Services.Knock.trigger/3
    (customer_api 1.21.0+88574494) 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