25115267 CustomerApi.Jobs.PublishNotificationJob
Queue notifications
Attempt 5 of 5
Priority 0
Tags ...
Node customer_api@10.10.1.109
Queue Time 00:00.222
Run Time 00:00.007
Inserted 10h ago
Scheduled 10h ago
Completed
Cancelled
Discarded 10h ago

Args

%{
  "account_id" => "207061",
  "data" => %{
    "account_insight_agent_id" => "7dfbf4c1-0785-4e49-a2cc-e29564d43092",
    "insights" => [
      %{
        "action_plan" => "Update the copy in the published flow to correct the three phrases above. After editing, proofread the rest of this dashboard tour for similar small spelling issues, since multiple typos appear in separate steps.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "5e69b763-be40-4da8-8f5a-276520c3ee03",
        "entity_type" => "flow",
        "expected_impact" => "Removing visible typos should improve credibility and polish for users seeing this dashboard walkthrough, supporting engagement.",
        "finding" => "I found likely spelling issues in the live flow **Dashboard Overview - Salesreps**.\n\nPotential typos:\n- **\"digestable\"** → likely **\"digestible\"**\n- **\"Check our the total dollar amount...\"** → likely **\"Check out the total dollar amount...\"**\n- **\"who bough it\"** → likely **\"who bought it\"**\n\nReview the live flow here: [Dashboard Overview - Salesreps](https://studio.appcues.com/flows/5e69b763-be40-4da8-8f5a-276520c3ee03/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "Dashboard overview flows have multiple visible copy typos",
        "type" => "issue"
      },
      %{
        "action_plan" => "Correct the repeated spelling issues in this variant as well. Since this flow appears to be a parallel version of the sales rep tour, compare the two dashboard overview flows side by side and standardize corrected copy across both.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "9b47a1d5-69fa-41a8-a4ab-a0dddd641d41",
        "entity_type" => "flow",
        "expected_impact" => "Consistent, typo-free copy across role-based variants should reduce confusion and make the experience feel more trustworthy.",
        "finding" => "The live flow **Dashboard Overview - Admin & AR** appears to contain several typo candidates.\n\nPotential typos:\n- **\"digestable\"** → likely **\"digestible\"**\n- **\"Check our the total dollar amount...\"** → likely **\"Check out the total dollar amount...\"**\n- **\"who bough it\"** → likely **\"who bought it\"**\n\nReview the live flow here: [Dashboard Overview - Admin & AR](https://studio.appcues.com/flows/9b47a1d5-69fa-41a8-a4ab-a0dddd641d41/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "medium",
        "title" => "Admin dashboard tour repeats the same typo pattern",
        "type" => "issue"
      },
      %{
        "action_plan" => "Confirm the preferred brand capitalization with your team, then update this flow if **UniPro** is the approved style. It may be worth checking related Supplier Connect flows for the same casing pattern.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "1c15cae5-3cc3-4187-8d53-5e0739fd3529",
        "entity_type" => "flow",
        "expected_impact" => "Consistent brand formatting strengthens trust and keeps onboarding copy aligned with the rest of the product experience.",
        "finding" => "In **Unipro Supplier Connect Welcome Flow**, the phrase **\"Unipro's Universal Product Catalog\"** may be a brand-style inconsistency. Elsewhere in live experiences, the brand is written as **\"UniPro\"**.\n\nSuggested correction:\n- **\"Unipro's Universal Product Catalog\"** → likely **\"UniPro's Universal Product Catalog\"**\n\nReview the live flow here: [Unipro Supplier Connect Welcome Flow](https://studio.appcues.com/flows/1c15cae5-3cc3-4187-8d53-5e0739fd3529/analytics)",
        "outcomes" => ["engagement"],
        "priority" => "low",
        "title" => "Supplier Connect welcome flow may have brand capitalization inconsistency",
        "type" => "issue"
      },
      %{
        "action_plan" => "Remove the extra **\"to\"** in that step, then scan the rest of the Showcase tour for similar copy-edit issues before the next publish.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "6c9e36e1-619e-441b-8ce1-4539c2f3ab3a",
        "entity_type" => "flow",
        "expected_impact" => "Fixing the sentence should make the instruction easier to read and reduce friction in a task-oriented walkthrough.",
        "finding" => "The live flow **Showcase** includes a clear duplicated word:\n\n- **\"click Link to Catalog to to match...\"** → likely **\"click Link to Catalog to match...\"**\n\nReview the live flow here: [Showcase](https://studio.appcues.com/flows/6c9e36e1-619e-441b-8ce1-4539c2f3ab3a/analytics)",
        "outcomes" => ["engagement", "activation"],
        "priority" => "medium",
        "title" => "Showcase tour contains a duplicated word in live copy",
        "type" => "issue"
      },
      %{
        "action_plan" => "Fix the subject-verb agreement and punctuation in these steps. Because this is instructional copy for admins, prioritize clarity and concise phrasing while updating.",
        "actions" => [],
        "cta_text" => "Review flow",
        "entity_id" => "4d8edb2d-03c1-419e-86f2-032e30916615",
        "entity_type" => "flow",
        "expected_impact" => "Cleaner instructional copy should make the setup flow feel more polished and easier to follow.",
        "finding" => "I found two likely copy issues in **Catalog Home - Admin**:\n\n- **\"Catalog or homepage banners allows you...\"** → likely **\"Catalog or homepage banners allow you...\"**\n- **\"appear on the top of the page,.\"** → likely **\"appear at the top of the page.\"**\n\nReview the live flow here: [Catalog Home - Admin](https://studio.appcues.com/flows/4d8edb2d-03c1-419e-86f2-032e30916615/analytics)",
        "outcomes" => ["engagement", "activation"],
        "priority" => "medium",
        "title" => "Catalog Home admin flow has grammar and punctuation issues",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "d507c80e-e810-4f14-9ae1-509ce5586abc",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

Attempt 5—10h 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—10h 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—10h 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—10h 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—10h 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