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

Args

%{
  "account_id" => "45545",
  "data" => %{
    "account_insight_agent_id" => "f953ade8-fa8d-4d15-9684-434513bf635b",
    "insights" => [
      %{
        "action_plan" => "Update the welcome flow copy to remove the visible spelling mistakes and any stray placeholder text. Prioritize the CTA typo first since it is the most user-facing error, then clean up the repeated sentence error and placeholder string.",
        "actions" => [],
        "cta_text" => "Review flow copy",
        "entity_id" => "-LYRcjE5hFp7xaDEwrfg",
        "entity_type" => "flow",
        "expected_impact" => "Fixing these errors should improve trust and polish in your first-run experience, especially for new users seeing onboarding content for the first time.",
        "finding" => "I found multiple likely typos in the live **Welcome to Qtego!** flow: \n- **\"Here are some tips to help you get you started.\"** → likely **\"Here are some tips to help you get started.\"**\n- **\"OK, Got ijt!\"** → likely **\"OK, Got it!\"**\n- **\"Whatkeverr\"** appears to be stray placeholder text and likely should be removed or replaced with the intended button label.\n\nReview the live flow here: [Welcome to Qtego!](https://studio.appcues.com/flows/-LYRcjE5hFp7xaDEwrfg/analytics)",
        "outcomes" => ["activation", "engagement"],
        "priority" => "high",
        "title" => "Welcome flow has visible spelling mistakes in live copy",
        "type" => "issue"
      },
      %{
        "action_plan" => "Since this looks like a duplicated experience, compare it against the main welcome flow and fix or retire the duplicated copy issues so both live versions do not keep showing the same mistakes.",
        "actions" => [],
        "cta_text" => "Compare duplicate flow",
        "entity_id" => "-M1g5F_e57FssNBR8gwu",
        "entity_type" => "flow",
        "expected_impact" => "Cleaning this up prevents duplicated onboarding experiences from carrying the same spelling issues into production.",
        "finding" => "The live **Copy of Welcome to Qtego!** experience contains the same typo pattern as the main welcome flow:\n- **\"Here are some tips to help you get you started.\"** → likely **\"Here are some tips to help you get started.\"**\n- **\"OK, Got ijt!\"** → likely **\"OK, Got it!\"**\n- **\"Whatkeverr\"** appears to be accidental placeholder text rather than intentional copy.\n\nReview the live flow here: [Copy of Welcome to Qtego!](https://studio.appcues.com/flows/-M1g5F_e57FssNBR8gwu/analytics)",
        "outcomes" => ["activation", "engagement"],
        "priority" => "high",
        "title" => "Published copy of the welcome flow repeats the same typo set",
        "type" => "issue"
      },
      %{
        "action_plan" => "Do an editorial pass on this live flow and fix the typo-level errors first, then review any remaining placeholder or draft-style text to make sure nothing unintended is still published.",
        "actions" => [],
        "cta_text" => "Review inventory flow",
        "entity_id" => "-LZB9u4GS18VoOcbTpGb",
        "entity_type" => "flow",
        "expected_impact" => "This should make the flow feel more polished and reduce confusion in a feature tour that explains complex setup steps.",
        "finding" => "The live **Inventory** flow has several phrases that look like typos or copy-edit issues:\n- **\"Enter an amount to for confirmation.\"** → likely **\"Enter an amount for confirmation.\"**\n- **\"import a previous events items\"** → likely **\"import a previous event's items\"** or **\"import items from a previous event\"**\n- **\"feel free to reach to our friendly Q\"** → likely **\"feel free to reach out to our friendly Q\"**\n\nI also saw placeholder-style copy such as **\"Hey, this is my button.\"** and **\"Hey this is some text for our header.\"**, which may not be typos but should still be reviewed in a live experience.\n\nReview the live flow here: [Inventory](https://studio.appcues.com/flows/-LZB9u4GS18VoOcbTpGb/analytics)",
        "outcomes" => ["activation", "engagement"],
        "priority" => "medium",
        "title" => "Inventory flow has several live typo-level copy errors",
        "type" => "issue"
      },
      %{
        "action_plan" => "Correct the misspelled term in the package flow and quickly scan the rest of the packaging guidance for similar copy-edit issues, since this experience contains a lot of instructional text.",
        "actions" => [],
        "cta_text" => "Review package flow",
        "entity_id" => "-La1j-N22Lz69XuxjgEq",
        "entity_type" => "flow",
        "expected_impact" => "Fixing the spelling improves professionalism in a flow that explains pricing and auction setup details.",
        "finding" => "The live **Inventory - Package** flow includes a clear misspelling:\n- **\"consingment company\"** → likely **\"consignment company\"**\n\nReview the live flow here: [Inventory - Package](https://studio.appcues.com/flows/-La1j-N22Lz69XuxjgEq/analytics)",
        "outcomes" => ["activation", "engagement"],
        "priority" => "medium",
        "title" => "Package flow includes a misspelled financial term",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "ac1321f6-b8ec-4538-8b07-c3681612fa6a",
  "workflow_key" => "insight-issue-added"
}

Meta

%{"orig_scheduled_at" => 1777558735747067, "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