25118890 CustomerApi.Jobs.PublishNotificationJob
Queue notifications
Attempt 5 of 5
Priority 0
Tags ...
Node customer_api@10.10.1.214
Queue Time 00:00.099
Run Time 00:00.005
Inserted 5h ago
Scheduled 5h ago
Completed
Cancelled
Discarded 5h ago

Args

%{
  "account_id" => "94742",
  "data" => %{
    "account_insight_agent_id" => "bb4afd1a-eeeb-4f09-b1c1-eb6db92f324d",
    "insights" => [
      %{
        "action_plan" => "For **“A Test For The Agent ok”**, rebuild this as one clear use case before treating it as live:\n1. Pick a single job for the flow — for example **discount promotion**, **favorites onboarding**, or **setup guidance** — and rewrite every step so the headline, body copy, CTA text, and tooltip all support that same outcome.\n2. Remove the leftover template body copy from the first modal and replace it with product-specific value messaging.\n3. Re-anchor the tooltip to a stable selector provided by your app team, ideally a semantic ID or `data-appcues` attribute, since Appcues docs recommend stable selectors for reliable tooltip delivery .\n4. Add a goal tied to the intended user action so you can measure whether the flow influences behavior; Appcues explicitly supports goals for flow success measurement .\n5. Because the current rule is still tied to a test page/domain and a custom trigger, review whether this experience should remain published at all until the message and targeting match a real production use case.",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => "d358068b-e1a4-4a05-8e72-f15af76691b3",
        "entity_type" => "flow",
        "expected_impact" => "A tighter single-message journey should improve user trust and comprehension, reduce dismissals caused by confusing copy, and make the flow measurable against a real activation or adoption goal.",
        "finding" => "I reviewed the published web flow **“A Test For The Agent ok.”**\n\nIts content is not coherent from step to step:\n- The opening modal headline promises **“Claim Your Discount Code”**\n- The body copy underneath is still **template/instructional text** about introducing a teammate or feature\n- The follow-up tooltip switches to **“Track your favorites”** with unrelated guidance\n\nThat makes the journey feel unfinished and undermines trust if a user does see it. The tooltip is also anchored to an exact full-class selector, which is a brittle targeting pattern. Appcues recommends using stable, semantic IDs or `data-*` attributes for element targeting instead of dynamic or fragile selectors, and recommends defining a goal so success can actually be measured  .",
        "outcomes" => ["activation", "adoption", "engagement"],
        "priority" => "high",
        "title" => "Published flow tells three different stories in one journey",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "8f3b5cb4-0eb6-485d-bddd-4d180bad4865",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

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