25363730
CustomerApi.Jobs.PublishNotificationJob
Queue
notifications
Attempt
5 of 5
Priority
0
Tags
...
Node
customer_api@10.10.1.109
Queue Time
00:00.281
Run Time
00:00.007
Inserted
3h ago
Scheduled
3h ago
Completed
—
Cancelled
—
Discarded
3h ago
Args
%{
"account_id" => "32626",
"data" => %{
"account_insight_agent_id" => "3dd40ab2-10df-4e50-a17d-fdaee0cbf203",
"insights" => [
%{
"action_plan" => "Update the sentence so the phrase reads **\"entry and utilise\"** with no broken spacing or formatting artifact. Since this is user-facing instructional copy, it is worth fixing quickly to avoid looking broken in production.",
"actions" => [],
"cta_text" => "Review typo",
"entity_id" => "5b0087db-3d04-4132-8a6a-f67d80d4fc53",
"entity_type" => "flow",
"expected_impact" => "Removes a noticeable credibility issue in a live tooltip and improves comprehension for users reading setup guidance.",
"finding" => "In **Tool Notification | Correspondence Register - Text Templates**, the live copy appears to split the word **\"and\"** into **\"an d\"** in the sentence:\n\n> \"Insert text templates directly into your correspondence register entry **an d** utilise placeholders...\"\n\nReview it here: [Tool Notification | Correspondence Register - Text Templates](https://studio.appcues.com/flows/5b0087db-3d04-4132-8a6a-f67d80d4fc53/analytics)",
"outcomes" => ["engagement"],
"priority" => "high",
"title" => "Live text-template tooltip contains a visible broken word",
"type" => "issue"
},
%{
"action_plan" => "Correct the duplicated punctuation in both Account Reconciler intro flows so the heading line reads **\"Open Beta means:\"**. Because these two flows share the same copy issue, review both before republishing any future draft changes.",
"actions" => [],
"cta_text" => "Review both flows",
"entity_id" => "de01e8d9-69ec-434a-a63e-cf4afea1c3d4",
"entity_type" => "flow",
"expected_impact" => "Improves polish and trust in a live beta announcement flow, especially for users evaluating a new tool.",
"finding" => "Both live Account Reconciler intro experiences use the phrase **\"Open Beta means::\"**, which looks like a typo. The likely correction is **\"Open Beta means:\"**.\n\nAffected live experiences:\n- [Tool | Intro Video | Account Reconciler Tool (BETA)](https://studio.appcues.com/flows/de01e8d9-69ec-434a-a63e-cf4afea1c3d4/analytics)\n- [Tool | Intro Video | Account Reconciler Tool (BETA) - FOR HELP LINK](https://studio.appcues.com/flows/831ce014-c1ee-42ed-b977-d0ba7b0a975b/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "Account Reconciler intro flows show a punctuation typo live",
"type" => "issue"
},
%{
"action_plan" => "Update the CTA copy to **\"Ok, let's go!\"** so the opening step reads naturally and consistently with standard English contraction usage.",
"actions" => [],
"cta_text" => "Review button copy",
"entity_id" => "efd22501-2389-46f5-ab9e-4864ffda3b14",
"entity_type" => "flow",
"expected_impact" => "Improves perceived polish at the start of a guided tour, where first impressions matter most.",
"finding" => "In **Setup | User | Customise User Profile [React]**, the primary button currently says **\"Ok, lets go!\"**. In this locale and context, the likely correct spelling is **\"Ok, let's go!\"**.\n\nReview it here: [Setup | User | Customise User Profile [React]](https://studio.appcues.com/flows/efd22501-2389-46f5-ab9e-4864ffda3b14/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "User profile tour starts with “lets” instead of “let's”",
"type" => "issue"
},
%{
"action_plan" => "Review the User Management walkthrough copy for possessive/apostrophe fixes and the likely **Multi-Factor** spelling correction. This flow is instructional, so small language issues can make the guidance feel less trustworthy.",
"actions" => [],
"cta_text" => "Review walkthrough copy",
"entity_id" => "1732aa94-a634-40ba-abf0-cc61eef2ac2e",
"entity_type" => "flow",
"expected_impact" => "Cleaner admin-facing guidance should reduce friction and improve confidence during setup tasks.",
"finding" => "In **Setup | User Management [React]**, I found multiple likely typo-level issues in live copy:\n\n- **\"Mult-Factor Authentication\"** likely should be **\"Multi-Factor Authentication\"**\n- **\"Reset a users MFA\"** likely should be **\"Reset a user's MFA\"**\n- **\"Reactivate a users access\"** likely should be **\"Reactivate a user's access\"**\n\nReview it here: [Setup | User Management [React]](https://studio.appcues.com/flows/1732aa94-a634-40ba-abf0-cc61eef2ac2e/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "User Management walkthrough has several copy-level grammar typos",
"type" => "issue"
},
%{
"action_plan" => "Update the opening sentence to **\"Let's start with a super quick tour...\"** so the welcome message reads naturally and professionally for new admins.",
"actions" => [],
"cta_text" => "Review welcome copy",
"entity_id" => "b0b4c889-3e8f-4a71-8cfc-04984f8a66ed",
"entity_type" => "flow",
"expected_impact" => "Makes a prominent onboarding message feel more polished for first-time users.",
"finding" => "In **Setup | Welcome Message - New SuperAdmin [React]**, the copy says **\"Lets start with a super quick tour...\"**. The likely correction is **\"Let's start with a super quick tour...\"**.\n\nReview it here: [Setup | Welcome Message - New SuperAdmin [React]](https://studio.appcues.com/flows/b0b4c889-3e8f-4a71-8cfc-04984f8a66ed/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "New SuperAdmin welcome message contains a contraction typo",
"type" => "issue"
},
%{
"action_plan" => "Correct **\"walkthough\"** to **\"walkthrough\"** in the selector modal. Because this term is repeated in the experience, it is worth checking nearby copy for other inherited wording issues at the same time.",
"actions" => [],
"cta_text" => "Review typo",
"entity_id" => "4ad4bff1-98e2-4a78-9011-be99315113ec",
"entity_type" => "flow",
"expected_impact" => "Improves clarity and professionalism in a central onboarding navigation experience.",
"finding" => "In **Setup | Walkthrough Select | SuperAdmin [React]**, the sentence says **\"select the walkthough you would like to trigger\"**. The likely correction is **\"select the walkthrough you would like to trigger\"**.\n\nReview it here: [Setup | Walkthrough Select | SuperAdmin [React]](https://studio.appcues.com/flows/4ad4bff1-98e2-4a78-9011-be99315113ec/analytics)",
"outcomes" => ["engagement"],
"priority" => "medium",
"title" => "Walkthrough selector contains a misspelled keyword in live copy",
"type" => "issue"
}
]
},
"notification_id" => "a17adc30-0424-48cb-8874-26b412ebda94",
"workflow_key" => "insight-issue-added"
}
Meta
%{"orig_scheduled_at" => 1777557944418015, "structured" => true}
Errors
Attempt 5—3h 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—3h 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—3h 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—3h 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—3h 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