24351223 CustomerApi.Jobs.PublishNotificationJob
Queue notifications
Attempt 5 of 5
Priority 0
Tags ...
Node customer_api@10.10.1.214
Queue Time 00:00.175
Run Time 00:00.005
Inserted 7d ago
Scheduled 7d ago
Completed
Cancelled
Discarded 7d ago

Args

%{
  "account_id" => "209385",
  "data" => %{
    "account_insight_agent_id" => "9da27368-643e-43b5-9ca6-1c57e8436300",
    "insights" => [
      %{
        "action_plan" => "### Recommendations for Re-Onboarding\n- **Prioritize cleanup of live flows with zero or near-zero performance**: Audience - intro - FTU, Create a scheduled campaign - date v3, Rebranding, and Segments - intro - no end should be reviewed first.\n- **Investigate error-heavy flows before the call**: Create a scheduled campaign - no end date and Audience - intro - FTU have the clearest evidence of delivery or UX issues hurting performance.\n- **Remove or retire QA/test content from the live experience set**: QA - Email - FTU - no end is still published and looks out of place for a customer-facing re-onboarding experience.\n- **Reduce the draft/archive backlog** by identifying webinar, duplicate, and test flows that can be permanently retired or ignored during re-onboarding planning.\n- **Use the re-onboarding call to define a smaller, intentional live portfolio** focused on a few high-value onboarding journeys instead of maintaining a large backlog with only 8 active flows.",
        "actions" => [],
        "cta_text" => nil,
        "entity_id" => nil,
        "entity_type" => "flow",
        "expected_impact" => "Cleaning up low-performing live flows and reducing stale inventory should make the account easier to manage, improve onboarding quality, and create a clearer foundation for activation and adoption improvements.",
        "finding" => "Based on the audit of **Connect - Acoustic, L.P**'s account, here are the insights on your Flows.\n\n**Important data note:** Appcues read tools do **not** currently expose exact total `flow_started`, `flow_skipped`, and `flow_completed` event counts for every flow in this audit. The published-flow table below uses the closest available verified metrics: **unique users who saw, skipped, and completed** each flow over the last **365 days**. Completion rate is calculated as **completed users / seen users**.\n\n### Published Flows\n\n| Flow Name | Date Published | Last Updated | Users Started | Users Skipped | Users Completed | Completion Rate (%) | Error Count | Tag Ids |\n|---|---:|---:|---:|---:|---:|---:|---:|---|\n|  Insights - email dashboard intro - no end | 2026-02-04 | 2026-02-04 | 337 | 285 | 71 | 21.1% | 0 | 217fc126-0c14-46b1-9f4c-c3906d0db560 |\n| Audience - intro - FTU | 2026-02-25 | 2026-02-25 | 861 | 640 | 0 | 0.0% | 191 | None |\n| Create a scheduled campaign - date v3 | 2025-02-13 | 2025-02-13 | 3 | 3 | 0 | 0.0% | 2 | None |\n| Create a scheduled campaign - no end date | 2026-03-06 | 2026-03-06 | 702 | 607 | 35 | 5.0% | 289 | None |\n| Insights - SMS dashboard intro - no end | 2026-02-04 | 2026-02-04 | 14 | 12 | 2 | 14.3% | 0 | 217fc126-0c14-46b1-9f4c-c3906d0db560 |\n| QA - Email - FTU - no end | 2025-11-05 | 2025-11-05 | 6 | 5 | 2 | 33.3% | 4 | None |\n| Rebranding | 2026-03-05 | 2026-04-02 | 520 | 491 | 0 | 0.0% | 11 | None |\n| Segments - intro - no end | 2026-02-04 | 2026-02-04 | 648 | 606 | 4 | 0.6% | 27 | None |\n\n### Non-Published Flows\n\n| Flow Name | Status | Last Updated |\n|---|---|---:|\n| [Appcues Services] Product Catalog Tour | Draft | 2026-04-14 |\n| Create segment | Draft | 2026-03-02 |\n| test nav | Draft | 2026-02-24 |\n| Copy of  Insights - email dashboard intro - no end | Draft | 2026-02-04 |\n| Copy of Audience - intro - FTU | Archived | 2026-02-04 |\n| Version 2 of Segments - intro - no end | Archived | 2026-02-04 |\n| Webinar - Message creation - 1-17 Oct | Archived | 2026-02-04 |\n| Insights - mobile dashboard intro - no end | Archived | 2026-02-04 |\n| Insights - executive dashboard intro - no end | Archived | 2026-02-04 |\n| ref sets | Archived | 2026-02-04 |\n| Insights - Audience health dashboard | Archived | 2026-02-04 |\n| Insights - whatsapp dashboard intro - no end | Archived | 2026-02-04 |\n| QA - Segments - FTU - no end | Archived | 2026-02-04 |\n| QA Insights - email dashboard intro - no end | Archived | 2026-02-04 |\n| Webinar - From basics to brilliance: Navigating Insights dashboards in Acoustic Connect - 21 - 26 August | Draft | 2025-08-22 |\n| Webinar - Data foundations for smarter marketing in Acoustic Connect - 24 July -  21 August | Draft | 2025-07-31 |\n| Email - FTU - no end | Draft | 2025-07-24 |\n| Webinar - Discover new possibilities for customer engagement with Acoustic Connect - 8 July -  17 July | Draft | 2025-07-24 |\n| Webinar - Getting started with Acoustic Connect - 22 May -  30 June | Draft | 2025-06-30 |\n| Segments advanced | Draft | 2025-06-16 |\n| Segments - advanced - no end | Draft | 2025-06-16 |\n| Connect - what's new - July 2025 | Draft | 2025-06-12 |\n| Webinar - Make smarter marketing decisions with behavioral intelligence - 24 April -  22 May | Draft | 2025-05-22 |\n| May 21 | Draft | 2025-05-21 |\n| test sh | Draft | 2025-05-15 |\n| Copy of Webinar - Mastering the basics of Acoustic Connect - 17-24 Apr | Draft | 2025-04-24 |\n| Copy of QA - Email - FTU - no end | Draft | 2025-04-22 |\n| Notice - Happy Customer Appreciation Day - 17-19 Apr | Draft | 2025-04-22 |\n| Tips and tricks | Archived | 2025-04-18 |\n| Campaigns - Create a journey - date | Archived | 2025-04-18 |\n| QA - Audiences short - FTU - no end | Draft | 2025-04-18 |\n| AugustModel3 | Archived | 2025-04-18 |\n| QA - SMS messages - FTU - no end | Draft | 2025-04-18 |\n| Webinar - Mastering the basics of Acoustic Connect - 17-24 Apr | Draft | 2025-04-17 |\n| Webinar - Craft compelling email content to drive engagement - 28 March - 17 April | Draft | 2025-04-17 |\n| QA - ALL channels module - FTU - no end | Draft | 2025-04-15 |\n| " <> ...,
        "outcomes" => ["activation", "adoption", "engagement"],
        "priority" => "high",
        "title" => "Flow audit shows a small live portfolio with widespread underperformance",
        "type" => "issue"
      }
    ]
  },
  "notification_id" => "1b28a787-721e-4e9e-bc39-159a6696da6e",
  "workflow_key" => "insight-issue-added"
}

Meta

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

Errors

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