25368328
CustomerApi.Jobs.PublishNotificationJob
Queue
notifications
Attempt
5 of 5
Priority
0
Tags
...
Node
customer_api@10.10.1.109
Queue Time
00:00.338
Run Time
00:00.006
Inserted
2h ago
Scheduled
2h ago
Completed
—
Cancelled
—
Discarded
2h ago
Args
%{
"account_id" => "46248",
"data" => %{
"account_insight_agent_id" => "29f53019-c7fe-40f1-9815-c073455ccf3e",
"insights" => [
%{
"action_plan" => "Update the published copy in this flow so the tooltip title reads **Monthly & Quarterly** and the intro copy uses **anyone else's radar**. Because this is a live Flow 2.0 experience, it is a good candidate for a direct copy cleanup once you've confirmed the wording.",
"actions" => [],
"cta_text" => "Review flow copy",
"entity_id" => "-LaWQwolu9DYDQAoE5-Z",
"entity_type" => "flow",
"expected_impact" => "Cleaning up these errors should improve trust and polish for users seeing this tour, especially on a prominent reporting page.",
"finding" => "I reviewed the live flow **Movers & Shakers** and found likely typos in published copy.\n\nPossible typos:\n- **\"Monthy & Quarterly\"** → likely **\"Monthly & Quarterly\"**\n- **\"on anyone elses radar\"** → likely **\"on anyone else's radar\"**\n\nReview it here: [Movers & Shakers](https://studio.appcues.com/flows/-LaWQwolu9DYDQAoE5-Z/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "Movers & Shakers has two visible spelling errors",
"type" => "issue"
},
%{
"action_plan" => "Prioritize this flow for copy QA. It has multiple user-facing spelling issues in one live experience, so fixing them together would be the cleanest approach. Double-check whether the first phrase should be **Your dashboard** or **You're** before updating.",
"actions" => [],
"cta_text" => "Review dashboard flow",
"entity_id" => "0981a71a-5b76-40fb-a32d-7a04f53b63ce",
"entity_type" => "flow",
"expected_impact" => "Removing several obvious errors in one dashboard tour should noticeably improve credibility and reduce friction during onboarding.",
"finding" => "I found several likely typos in the live **Advertiser Dashboard** flow.\n\nPossible typos:\n- **\"Youre dashboard\"** → likely **\"Your dashboard\"** or **\"You're on your dashboard\"** depending on intent\n- **\"Cilck on the individual events\"** → likely **\"Click on the individual events\"**\n- **\"rigtht pane\"** → likely **\"right pane\"**\n\nReview it here: [Advertiser Dashboard](https://studio.appcues.com/flows/0981a71a-5b76-40fb-a32d-7a04f53b63ce/analytics)",
"outcomes" => ["activation", "engagement"],
"priority" => "high",
"title" => "Advertiser Dashboard contains multiple obvious typos",
"type" => "issue"
},
%{
"action_plan" => "Review this tour's tooltip copy and correct the clear spelling/grammar issues first. While you're in the flow, it would also be worth doing a quick pass for brand-style consistency like **YouTube** capitalization.",
"actions" => [],
"cta_text" => "Review enterprise profile flow",
"entity_id" => "-LZfkHoJGpgncVo_unhH",
"entity_type" => "flow",
"expected_impact" => "A cleaner enterprise tour should improve perceived quality for high-value users and reduce distraction during feature education.",
"finding" => "The live **Advertiser Profile - Enterprise** flow appears to contain a few likely typos or grammatical errors.\n\nPossible typos:\n- **\"the ad is probably peforming well\"** → likely **\"the ad is probably performing well\"**\n- **\"Click on the name a campaign\"** → likely **\"Click on the name of a campaign\"**\n- **\"Youtube Channels\"** may need brand-correct capitalization: **\"YouTube Channels\"**\n\nReview it here: [Advertiser Profile - Enterprise](https://studio.appcues.com/flows/-LZfkHoJGpgncVo_unhH/analytics)",
"outcomes" => ["activation", "engagement"],
"priority" => "medium",
"title" => "Advertiser Profile - Enterprise has copy errors in live tooltips",
"type" => "issue"
},
%{
"action_plan" => "Correct these terms in the tooltip copy, then scan the rest of the tour for duplicated text blocks since this flow appears to reuse repeated instructional patterns.",
"actions" => [],
"cta_text" => "Review publisher flow",
"entity_id" => "-LaXE6MH3RXOKPkhHLo_",
"entity_type" => "flow",
"expected_impact" => "Fixing these errors should make the tour feel more polished and easier to trust while users explore publisher data.",
"finding" => "I found likely typos in the live **Publisher Profile - Enterprise** flow.\n\nPossible typos:\n- **\"segmeneted\"** → likely **\"segmented\"**\n- **\"Advertisers and Publishers ls\"** → likely **\"Advertisers and Publishers list\"**\n\nReview it here: [Publisher Profile - Enterprise](https://studio.appcues.com/flows/-LaXE6MH3RXOKPkhHLo_/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "Publisher Profile - Enterprise includes repeated copy mistakes",
"type" => "issue"
},
%{
"action_plan" => "Since this looks like duplicated profile-tour copy, review it alongside the enterprise version and standardize the corrected wording across both variants.",
"actions" => [],
"cta_text" => "Review non-enterprise flow",
"entity_id" => "-LcCS8dsEUHtKEirAoGh",
"entity_type" => "flow",
"expected_impact" => "Fixing mirrored copy issues across account tiers will keep the onboarding experience consistent and reduce avoidable quality issues.",
"finding" => "The live **Advertiser Profile - Non-Enterprise** flow appears to repeat several copy issues found in related profile tours.\n\nPossible typos:\n- **\"segmeneted\"** → likely **\"segmented\"**\n- **\"the ad is probably peforming well\"** → likely **\"the ad is probably performing well\"**\n- **\"Click on the name a campaign\"** → likely **\"Click on the name of a campaign\"**\n\nReview it here: [Advertiser Profile - Non-Enterprise](https://studio.appcues.com/flows/-LcCS8dsEUHtKEirAoGh/analytics)",
"outcomes" => ["activation", "engagement"],
"priority" => "medium",
"title" => "Non-enterprise Advertiser Profile repeats enterprise copy errors",
"type" => "issue"
},
%{
"action_plan" => "Update the duplicated publisher-tour copy so the non-enterprise version matches any corrected enterprise wording. A side-by-side review will likely catch any other inherited issues quickly.",
"actions" => [],
"cta_text" => "Review non-enterprise publisher flow",
"entity_id" => "-LcCT8lPcVc7K0skXaQk",
"entity_type" => "flow",
"expected_impact" => "Cleaning up mirrored errors should improve consistency and reduce polish gaps across plan-specific experiences.",
"finding" => "The live **Publisher Profile - Non-Enterprise** flow contains the same likely typo pattern as the enterprise version.\n\nPossible typos:\n- **\"segmeneted\"** → likely **\"segmented\"**\n- **\"Advertisers and Publishers ls\"** → likely **\"Advertisers and Publishers list\"**\n\nReview it here: [Publisher Profile - Non-Enterprise](https://studio.appcues.com/flows/-LcCT8lPcVc7K0skXaQk/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "Non-enterprise Publisher Profile mirrors existing typo issues",
"type" => "issue"
}
]
},
"notification_id" => "d6728770-c2c5-45f3-ae72-ae53e5cc9d9c",
"workflow_key" => "insight-issue-added"
}
Meta
%{"orig_scheduled_at" => 1777558722350087, "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