Failure PatternDecision layer
The dassi Browser-Session Trap: Why Agencies Fail When Client Workflows Depend on an Open Tab
Symptom: Client reports that payout reconciliation ran at 9am but the browser was closed at 8:55, so the task silently skipped and no alert fired. Root cause: dassi executes only while the browser is open, so any workflow scheduled against a true server clock will miss runs whenever the client closes Chrome, Edge, or Brave at end of day.
By InnovaAI ResearchPublished Updated
How do you recognize it?
- •Client reports that payout reconciliation ran at 9am but the browser was closed at 8:55, so the task silently skipped and no alert fired.
- •An agency delivery lead discovers dassi is still signed into a former contractor's Chrome profile, and the client's ATS updates stopped three weeks ago.
- •Approval-rule flags were never configured, so dassi submitted a supplier form with stale pricing because nobody paused the flagged action.
- •The client's monthly invoice shows dassi Pro at $100/month, but the agency is only billing a $1,800 Task Starter Pack with no recurring line item for workflow refinement.
- •Run history shows the same applicant-screening job executed twice because the schedule was set in the client's local timezone and the agency assumed UTC.
Why does it happen?
- •dassi executes only while the browser is open, so any workflow scheduled against a true server clock will miss runs whenever the client closes Chrome, Edge, or Brave at end of day.
- •The agent operates inside accounts the client is already signed into, which means session expiry, password rotation, or a departed employee's profile silently breaks delivery with no vendor-side integration to fail loudly.
- •Agencies quote the $1,800 setup fee and stop there, ignoring that dassi's Starter tier at $25/month (or $21/month annual) and Pro at $100/month (or $83/month annual) are per-seat costs that must be folded into a retainer or the margin evaporates.
- •Plain-English job definitions are easy to teach once but hard to audit, so agencies skip approval rules and timezone settings during the 15-30 minute setup and inherit unpredictable execution.
How do you fix it?
- •Open dassi's schedule panel for every client job and set the run window to a time the client's browser is reliably open, then add a second fallback run 30 minutes later.
- •In the approval rules section, flag every action that touches money, submissions, or external communications so dassi pauses instead of executing unattended.
- •Audit each client's dassi profile against the browser account it is signed into, and reassign or re-authenticate any job tied to a contractor or shared machine.
- •Add a recurring line item to the client retainer that covers the dassi seat cost plus 1-2 hours of monthly workflow refinement, priced against the Starter $25/month or Pro $100/month tier actually in use.
More on dassi
- StrategyWhy dassi Turns Browser Sessions Into Agency Retainers
- Evaluation Ruledassi Rule: Adopt Only When the Client Has 3-5 Repeatable Browser Tasks and a Machine That Stays Awake
- Decision Frameworkdassi: Buy vs Skip (Browser Agent Retainers at $25 to $300 per Month)
- Implementation Blueprintdassi Recurring Task Retainer (5-7 days)
- Operating Proceduredassi Client Workspace Setup (Onboarding)
More for AI Agents
- Failure PatternsThe B2B Rocket Multichannel Overload Trap
- Failure PatternsWhy Agencies Fail With Activepieces in Multi-Client Deployments
- Failure PatternsThe Productized Agent Trap: Why AI Agent Services Stall Without Client-Specific Wiring
- Failure PatternsThe Agent-as-Product Trap: Why AI Agent Services Stall Without Client-Specific Wiring