19793275
CustomerApi.Jobs.Insights.ExecuteAccountInsightAgentJob
Queue
insight_agents
Attempt
2 of 2
Priority
0
Tags
...
Node
customer_api@10.10.1.109
Queue Time
00:00.217
Run Time
00:43.563
Inserted
1h ago
Scheduled
1h ago
Completed
1h ago (00:44)
Cancelled
—
Discarded
—
Args
%{
"account_id" => "34567",
"account_insight_agent_id" => "da0f9b3e-2ed3-4a0b-a1bf-63344873f9f0"
}
Meta
%{
"deps" => [],
"name" => "execute",
"on_hold" => false,
"orig_scheduled_at" => 1772732400744355,
"partition" => true,
"partition_key" => "eXIne95kph4mxcz2c3GeIS2C5got2yB3axt1XTOWow8",
"recorded" => true,
"return" => "g1AAACGCeJylWUuvHEcZTYhDEkeINbvaOJppZsa+1w4kdxM5l1gy5IHsG0WwsWq6a2bK069Udc94sgAvEIIVEiwiEEisWPEDWLHhn/gP8Bc456vqx51re4ElcO501+t7nXPq6+a11157ff89W3q73jT+UaYbnePZtQb/XC/wz7s6bWxVPqpzXeL3mzfvWeebmdrp3GK0UfuNaTbGqWZjvcL/tEqc0bmqXZW1aaOW+LVN1M443/Jt43S6teX65rrCqLQqV3bdOs1NMN23ZqHONybdYkHd4B+jeIJdGGB2pmxUZla2tHGG8o3NuZBzBttNwpBSF2bGM9TGNdb4mdJlhv8flDNft9YZ/GgaZ5dtY/x0oe6v1KFq8TLF7JyjuEIWNsTsdKPLNX+XO+uqsuBTNfGNXsMU9ey3fxR7pzNVOVVUmV1ZDMaKTum22ahVXu1nwVhXvMSyYAsGGa9WWEqrbVntYWbZGFfCXzhto1pv3OL69c/NEwTC+ipnHLjeStu8dYYnMJgjz8wTuMCaMjWq1s1moR6YnTV7eVeVy0q7jCZ8eV/FQz17+tfzqizpTKaD8rAiNc+e/g2nM7X4sTOEB/Fqo3cwRaW50U6VOJQKOYNYLNYLRsEW2h3U+cXd2eB+nKpAvDEuBsc4V7k5XApjCuO9uDaERnzI9Cp3Vb4zGSZkGS3LbWobtW6RijDwDMkII0YrKw1vlMZknCMvm0pllbJYM02xCVfNTGllTWYIfJjnS6SochVyo7MBTnm4tbUEBRGhN34YR2BFrXJb2AZWIZ/gFb3MTV8AYtEU8bpnEcH8EA6PCNs8hAULLCsYeBQtHqcw2iOgTDc4oqhz+RP7rVvEzSHcZ7QlxgGu0GVwljhzxr+rAgmWcmPlN9Uec5HkFcrxEL2MEraYoVVmpYJyW255Jm+aBhHw0S+Y7BrUAUozt0jCaoU8fWI8zlUisxx2MHmwDYOxRZkx6KMUl4If/HkOYKDLVgQUeusxdqdjv3jA17AWG+K917RbchFvp8jH8aIjD8GwQgPK+KzEyVdtLmVFiCp5KDzLjdTSOgKOZDRSoDHcTTsLLy3zKt2abKE+qwAylQuV1aIichyCI9oSZaoecu4paoHHk9WcaVqH/RlQ7Q0caRbE0LfTRj9qUBj8MYn1d+yY98bVSLzg4Hdglm0Oj2y2f6O0uQByfNQcatM//D7zJoW3Htmixsp89s0DYEXluNzVozKmqMI25WtmzNyZXMKRATPn1WrlGfE2zxRWdMgXlSTDkZNkWAFJqx28km5gvHLWb8Xot4DRtAV/v/6PJLmI9OAPJfyJjAxQJggzKatGPJbBBxE107SCm6eLJCHQ7WOKs5w7Kzq7TtQkCbmk9pXbethvkqlUYsPAJwlhkUHBoHTzXOCFPZNEmE35VoCByRNzUqUhUxMW8RzrxW0Hd55hfpJ8cHoDp+0HnF4ZcPJhGPBZhX3wssD2nbtVXSExzzDqhfiLNTyOYkos8QnrGy4kIDQos4m3RSsBnHKNO7dObt65dXuEBZ6za0vmRURBbRaDETW9ArNER0quAtNwNOMpA77DJ9cHZ8lPVDbJHD8fywTAO7KsOfDHtQ10BP94EzmKs+Gvz5/95e///dcf1N3B5bGYdF0jczwUQrVlgcpJRkXggxcnkihRokxlF+a+7KJz0PsLtcr2YaOBWUsgH5hC0CxmV1kiu9KAGnB7BZedPnv6JzosE/Sde9QTWDyF0HFWg+2TZKHuEf27ZJwpgMZGe/uNEXARlELw9puDAhIDdmGPD7wJXwfgFihFcc9XzgaSDPAntg7YeOFkDQHmI/wLpxh4IutOs6pSCKwqsH6qa70EwTRAqxpolwU+aWxhsOBOcH3Y7oGBy1DI4pxCly3wiLVEGKKOQCqDabc+7B+1UqD9rCDi7kADhSmWchAkiLeZccIDZAZUZvRikD7wrd76yDFtfXNM2KJ6ZFEU2wXql5TyuPXNMT1mINB1GcpaUCit1hSFOFRe6UzM7aCLUyl+ODr4G/KVSrMzfG1KrJtijfrQ0aHomVnHGiMRc4kQly14j7jZkeISS61sA4fcBRVWNYMMdw6MSH6F8+H2T7EBGKxyrO6gMQxtlICLsxWcF8Q1iD111V4Kg+aQ6aKgQzyEogBSFH9RYfnL2noW1UrA0UD1KH84hHMB/mbH+PSkH5AmeLFM8zYzvck451cMI5Lg2dM/Q69SYEmem5DSWLR2nVTX2dyUmR/rn8jZCGxwT9Tpee/6nKW+N/y3w+OR6F+oC94hztTkZNprmPOLBzM1OZ0q1H5AjzhP0m+S2aynEMcciWK3c1owdxpE4OT2lKwhiTLSEgFdgKNRWXdzYx1FllCuzXH1cJp6gBJmRtkq4jCt8lwvoTNAy6ijL/0IODZVniFAvD/cvflxACwphhPg0qnaG7MNSmxrgBTcfm+Bom6hvtgxQSzvOyz0trsMXAU5zZSgDmnD/ayoY0F2SFyVjEFQS/QWCTupShOV/14fErXCPLzs8jA64arO+UHkZG/WPAHM75D0VYXN7z82hFYFcF8HHSB3EpariRcQnhcAc6ij8s3tqqGAiQl305RrJE0RmF/k0OArT8KIfPCfb5P+6tqWgynLXHuU+LHO+fer6Zxf8Amqi3rnXvAry6pLcay6NJLaG94JQZs6YzlR6QwGcRjCzHusk3y0on0LLZdkFrComM/ioqKJKBlObt26QfwStu9wYjIyeira5ZxEMG82QJP1RoqLk28v7mAyHIVdwrCLB0pD36yha/aISlzuskr5cPHBjaPRPbsejz1ZnHDsdfGvb9dreNVLBoIfzdhHkEOSnGQXB0uwSmNZYiGjYQpjLLcrupgUCfAzeQjnVf3zdpc1on4GR19VP9+lrGqLy/rnl/dLIoMf8KKHPQqT4N1emVyN/qUyfokWereqiTYtMPLwIkV07Z+xe9OwNkPLRkvLZmlA57CETAVa1XlyiXq6y9OcahM5rXPtioU6B4QESc68ksLRKdjHh+ZMUK4zxd1ZjCbAqwDr3BthfNXtzIB1fQW5qceWS2gA9Lfp8BQlYIFZWd+wAanouqcyeluaU7Jm4Gk4EfRrjegOyBM4fXUYda84k6nBM2W46UtDifnnO1bqJWEvjZYg9YKx20CymmiCaH6DInsolD8SZg7VC0hPO+xMkg1EWjPHM1mlJxgBZVBoBo3oR+eaCPPIfZWaEabDouosEIysgDe6KKThIPpDCzMAASPcB5HNzVkNoG8fBRESr2PMomKuMfeOmE13N6JZEEzxYaC5aTg1mzJyCacMHghPenVBjcEVscRwxdbbQFaBIgPPdNIYGsif0Q3zFbtisegZ9CpnRy9FEjKGVzpJACEEx2+RInQKw0dqrVEbyJvo/NhEA544xMiOeitB5Qxeh2sgp9KWXPZ1S/FJ35CbA1LtNxUlfp7HVBWcwcVAEe5xOIYXp+amW3PommM8FaX1HfDMnQ/A/y21c2zRjAWQM0iOTK5Ggdzyam1Fmd1k1TgLt1BrD60ZeDI2GdkZMwKTRSf1ZImliXeOqKUu1UFn5RCwiZ6OmwfV6tgYUU3LqciU+UlshATpVe3isrJxuGX1eGHgG8N45nIvbZgaHbFdlRTv3QUwHb4Z8Oa92ErrIhWS/FX1xW/ui9080fONHqX1znQuiN2SqDQGR4SjxYZJBuL2BN8CYy6JkFW8WkbTrkiLb19NWnx1dB4wu+RuiBRN/TEWOvgIEOSAtp4GOjVBUPPse+BcJ38LdjEC/o6Fxc9JiB3qHruBTH4aSf9TLcd/yciuX/KxlcqXXol8YhCpMBRfklDe0wMRRgYYHKn1cM8OrINFv+ynd5AtXcewQDedhY4j8a6lGdZf3X7/BntFgzZ5vmZ4p7fj/xMN9z+RltoQLrbVzo7Ka2DOcYhephGucZkXioOzKA6cWTlqqq6tjisTyVMlj6ulnzfVfGnmGW4FxxKB/U7t1F7n26gP2RsGyuA2juqp2wC+RnrPApKdjOxlXIPE5QcD48dQDMe1Xf01SIHbAJH3If89mwiEOeH+qmupDfTys+6uJCvU7Fr5puvDQCUcQvsAl8/+Y8XOapqiIblgmnSbQ6Kl" <> ...,
"structured" => true,
"uniq" => true,
"uniq_bmp" => [1, 0, 2, 3],
"uniq_key" => "zlD8OkCujVwh54+j9RhFRPZwDaFyXQlWTCWIKQLmk6w",
"workflow" => true,
"workflow_id" => "019cbf15-c468-7189-a260-a6866ed7cd13"
}
Recorded Output
%{
insights_data: [
%{
"action_plan" => "First, validate whether this is a *real product break* versus a tracking/goal configuration issue. Check that the activation event definition is still correct (event name, properties, and any required attributes). If you recently renamed events, changed environments (staging → prod), or modified your auth flow, confirm that the activation event still fires for a known internal test user.\n\nNext, isolate the failure mode in the experience path. Review the onboarding UI at the “Connect data source” step and confirm users have a clear next action (e.g., primary CTA, required permissions, and error-state messaging). If auth is involved, add explicit guidance: what permissions are needed, what to do if access is denied, and a fallback route (e.g., “Skip for now” + route to a limited but usable product state).\n\nFinally, add resilience to both the experience and measurement. Implement a guardrail: if users hit an auth error, automatically show a recovery message with a direct link to settings and a short checklist of fixes. In parallel, add a secondary activation goal (e.g., “Created first project” OR “Imported sample data”) so activation measurement remains meaningful even when a single integration step is temporarily blocked. Monitor the funnel daily until Step 2 completion returns to baseline.",
"cta_text" => "Review activation goal & onboarding flow",
"entity_id" => nil,
"entity_type" => nil,
"expected_impact" => "Restoring Step 2 completion and reducing auth-related drop-offs should improve **activation** and reduce early churn risk.",
"finding" => "**This is synthetic test data (not based on your account).**\n\nNew users are completing Step 1 (*Create workspace*) but then **fail to reach the activation event** (*First successful project created*).\n\n- **Step 1 completion:** **82%**\n- **Step 2 completion:** **19%**\n- Most common drop-off point: **“Connect data source”** screen\n- Error telemetry (simulated): **401/403 auth errors** spiking immediately after Step 1",
"outcomes" => ["activation", "conversion"],
"priority" => "high",
"title" => "⚠️ Activation funnel appears broken after onboarding step 2 (test insight)",
"type" => "alert"
},
%{
"action_plan" => "Start by splitting your announcement into **2–3 audience-specific variants**. For new users, emphasize a simple “why it matters” statement and a low-friction first step (e.g., “Try it with sample data”). For experienced users, focus on the capability upgrade and time savings (e.g., “Replace your manual workflow in 2 clicks”). If you have admins vs. members, consider a separate variant that speaks to setup/permissions for admins.\n\nThen, adjust the experience design to reduce cognitive load and improve the path to first value. Replace generic copy with a clear, single primary CTA and a short bulleted list of benefits. Add optional secondary links (“Learn more”, “See examples”) rather than crowding the main path. If the feature requires configuration, route users directly to the relevant settings screen and include a short “What you’ll need” section to prevent dead-ends.\n\nFinally, measure adoption properly with a lightweight success definition. Track: (1) message CTR, (2) landing success rate (did users arrive at the feature screen), and (3) **first meaningful action** in the feature (e.g., created rule, ran report, invited collaborator). Use a simple holdout or A/B split for 1–2 weeks and keep the winner. Over time, graduate the announcement into a contextual prompt that appears only when a user is *one step away* from using the feature.",
"cta_text" => "Create segmented variants",
"entity_id" => nil,
"entity_type" => nil,
"expected_impact" => "Better targeting and clearer next steps typically lift **adoption/engagement** on announcements by **2–3×** versus unsegmented blasts.",
"finding" => "**This is synthetic test data (not based on your account).**\n\nYour “New Feature” message is being shown broadly, but engagement is concentrated in a small cohort.\n\n- Message reach: **100% of active users (unsegmented)**\n- Click-through rate: **3.4% overall**\n- CTR among power users (simulated): **9.8%**\n- CTR among new users (simulated): **1.1%**\n\nThis suggests the same message is trying to serve multiple user intents and maturity levels.",
"outcomes" => ["adoption", "engagement"],
"priority" => "medium",
"title" => "Increase feature adoption by segmenting your “New Feature” announcement (test insight)",
"type" => "opportunity"
},
%{
"action_plan" => "First, treat this as a *behavioral signal* rather than a single-metric alarm. Compare cohorts by acquisition source, plan type, and first-session behavior to confirm what changed. If a product change shipped recently, map the release date to cohort boundaries to identify whether the retention dip correlates with a specific workflow becoming harder to complete.\n\nSecond, focus on reinforcing the **habit-forming action** that predicts retention (in this test scenario: inviting a teammate). Add a timely prompt after the user’s first “success moment” (e.g., created a project, generated a report) that explains why collaboration improves outcomes. Make the invite step frictionless: pre-fill suggested roles, clarify permissions, and allow skipping without punishing the user.\n\nThird, implement a short retention “rescue sequence” for users who stall. If a user has not performed the key action within 24–48 hours, show a lightweight reminder on next login and/or trigger a checklist item that guides them to the next best step. Track whether the sequence improves (a) completion of the key action and (b) week-1 return rate over the next 2–3 cohorts before rolling it out broadly.",
"cta_text" => "Analyze cohorts & add retention prompt",
"entity_id" => nil,
"entity_type" => nil,
"expected_impact" => "Improving completion of the key collaborative action should lift **week-1 retention** and downstream **engagement** for new cohorts.",
"finding" => "**This is synthetic test data (not based on your account).**\n\nWeek-1 retention (users returning 7 days after signup) is trending downward in the most recent cohort.\n\n- Prior cohort week-1 retention: **28%**\n- Latest cohort week-1 retention: **19%**\n- Biggest drop is among users who **did not invite a teammate** in the first session\n- Users who complete “Invite teammate” retain at **~35%** (simulated)",
"outcomes" => ["retention", "engagement"],
"priority" => "medium",
"title" => "Early retention risk: week-1 return behavior trending down (test insight)",
"type" => "risk"
},
%{
"action_plan" => "First, reframe guidance around *jobs-to-be-done* rather than a linear walkthrough. Instead of pushing every user through the same tour, present a short menu of the top 3–5 tasks that map to common outcomes. Keep the menu persistent and easy to reopen (e.g., via a launcher) so users can return when they’re ready.\n\nSecond, redesign the tour content into modular, outcome-based “micro-paths.” Each micro-path should be 2–4 steps max and end in an observable success action (e.g., “Import completed” or “Dashboard created”). Use concise copy, a single primary CTA per step, and optional “Need help?” links for deeper documentation. This reduces fatigue while still guiding users to value.\n\nThird, align measurement with intent. Track task selection rate, micro-path completion rate, and time-to-first-value for each task. Over time, personalize the task menu by role or lifecycle (new vs. returning) so users see the most relevant actions first. If you later reintroduce a longer tour, position it as optional (“See everything”) rather than the default path.",
"cta_text" => "Convert tour into task-based guidance",
"entity_id" => nil,
"entity_type" => nil,
"expected_impact" => "Task-based guidance generally improves **engagement** and can accelerate **time-to-value**, supporting better **activation** downstream.",
"finding" => "**This is synthetic test data (not based on your account).**\n\nWhen given a choice between a multi-step guided tour and a “jump to task” menu, users disproportionately choose self-serve.\n\n- “Start tour” click rate: **6%**\n- “Jump to a task” click rate: **21%**\n- Top selected tasks (simulated):\n 1. **Import data**\n 2. **Invite teammate**\n 3. **Create first dashboard**",
"outcomes" => ["engagement", "activation"],
"priority" => "low",
"title" => "Users prefer self-serve guidance over long tours (test insight)",
"type" => "insight"
}
]
}
Errors
Attempt 1—1h ago
** (Oban.PerformError) CustomerApi.Jobs.Insights.ExecuteAccountInsightAgentJob failed with {:error, %OpenaiEx.Error{status_code: nil, name: nil, message: "Connection closed.", body: nil, code: nil, param: nil, type: nil, request_id: nil, request: nil, kind: :api_connection_error}}