25478766
CustomerApi.Jobs.PublishNotificationJob
Queue
notifications
Attempt
5 of 5
Priority
0
Tags
...
Node
customer_api@10.10.1.109
Queue Time
00:00.112
Run Time
00:00.068
Inserted
51m ago
Scheduled
50m ago
Completed
—
Cancelled
—
Discarded
50m ago
Args
%{
"account_id" => "106160",
"data" => %{
"account_insight_agent_id" => "62e3b1cf-db85-43c3-82f1-0205b271a4b3",
"insights" => [
%{
"action_plan" => "Use the Loops insight to derive additional insights through one focused experiment design:\n1. Define the audience: **new users / first 14 days after first login** using properties like `first_seen_at` or a dedicated new-user segment \n2. Define the target behavior: one specific activation or feature-adoption event, such as **Created Project**, **Connected Integration**, or **Used [Key Feature]** \n3. Sequence **3 nudges** around moments of likely need, not just elapsed time\n4. Measure three layers separately: **reach**, **adoption conversion**, and **month-2 retention**\n5. Compare against a holdback/control group so you can tell whether the campaign actually caused any uplift \n\nBest next insight to derive after setup: identify **which key action most strongly correlates with month-2 retention**, then design the 3-message sequence around that action instead of around banners alone.",
"actions" => [],
"cta_text" => "Design the experiment",
"entity_id" => nil,
"entity_type" => nil,
"expected_impact" => "A controlled onboarding experiment should give you a clearer path to improving activation first, then retention, with evidence you can trust.",
"finding" => "The most useful way to process the Loops insight is to treat it as a **hypothesis**, not a conclusion:\n\n- Hypothesis: users who see **3 well-timed nudges within 14 days of first login** may adopt a key behavior more often, which could improve later retention\n- Risk: the cited **1.04% adoption** suggests the adopting group may be quite small, so a weakly targeted banner test could produce noisy results\n- Appcues guidance supports building around a narrow outcome, a clear audience, and a defined Goal, such as \"new users complete their first key action within 7 days\" \n- Appcues benchmark data shows **feature adoption averages ~34–36%**, and product-triggered nudges outperform batch-style messaging for adoption use cases ",
"outcomes" => ["activation", "adoption", "retention"],
"priority" => "medium",
"title" => "Turn the Loops claim into a controlled first-14-days experiment",
"type" => "opportunity"
}
]
},
"notification_id" => "a2a6b4f1-0649-4ea3-bd50-d58a47affbea",
"workflow_key" => "insight-opportunity-added"
}
Meta
%{"orig_scheduled_at" => 1777665386854537, "structured" => true}
Errors
Attempt 5—50m ago
** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-opportunity-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Fri, 01 May 2026 19:58:02 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKuJVnU9QBGCzcMChqDm"}, {"x-xss-protection", "1; mode=block"}], status: 404}}
Attempt 4—50m ago
** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-opportunity-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Fri, 01 May 2026 19:57:30 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKuJTvdMIPUPXHcC1bTE"}, {"x-xss-protection", "1; mode=block"}], status: 404}}
Attempt 3—50m ago
** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-opportunity-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Fri, 01 May 2026 19:57:06 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKuJSV-mKVPqGXgC1rmE"}, {"x-xss-protection", "1; mode=block"}], status: 404}}
Attempt 2—51m ago
** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-opportunity-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Fri, 01 May 2026 19:56:45 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKuJRKrb2W0kldICgngk"}, {"x-xss-protection", "1; mode=block"}], status: 404}}
Attempt 1—51m ago
** (Oban.PerformError) CustomerApi.Jobs.PublishNotificationJob failed with {:error, %Knock.Response{url: "https://api.knock.app/v1/workflows/insight-opportunity-added/trigger", body: %{"code" => "workflow_missing", "message" => "The workflow you specified was not found in this environment. Make sure you commit the workflow before trying to invoke it. See the docs: https://docs.knock.app/send-and-manage-data/environments", "status" => 404, "type" => "invalid_request_error"}, headers: [{"date", "Fri, 01 May 2026 19:56:26 GMT"}, {"content-type", "application/json; charset=utf-8"}, {"content-length", "278"}, {"connection", "keep-alive"}, {"access-control-allow-credentials", "true"}, {"access-control-allow-origin", "*"}, {"access-control-expose-headers", "authorization x-knock-user-token x-knock-environment"}, {"cache-control", "max-age=0, private, must-revalidate"}, {"x-content-type-options", "nosniff"}, {"x-frame-options", "SAMEORIGIN"}, {"x-request-id", "GKuJQED7qHoxXgUC07pG"}, {"x-xss-protection", "1; mode=block"}], status: 404}}