<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/propagated-sessions-oegd4csaa" -->

---
title: Propagated Sessions | daily.dev
description: Inngest sessions now propagate automatically to child runs triggered by events, invokes, or defers, so a whole run tree started from one root run is grouped...
canonical: https://daily.dev/posts/propagated-sessions-oegd4csaa
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Propagated Sessions | daily.dev
og:description: Inngest sessions now propagate automatically to child runs triggered by events, invokes, or defers, so a whole run tree started from one root run is grouped...
og:url: https://daily.dev/posts/propagated-sessions-oegd4csaa
og:image: https://api.daily.dev/og/posts/oEgD4Csaa.png
og:image:alt: Propagated Sessions
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Propagated Sessions

**[Inngest Blog](https://daily.dev/sources/inngest)** · 1 min read · 0 upvotes · 0 comments

## Summary

Inngest sessions now propagate automatically to child runs triggered by events, invokes, or defers, so a whole run tree started from one root run is grouped under a single session. This helps track AI agents and long-running workflows where a single user action fans out into multiple functions. The Sessions page shows run counts, failures, recent activity, and involved functions per session.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.inngest.com/changelog/2026-08-07-propagated-sessions>

## Questions this post answers

### Do Inngest sessions propagate to child runs triggered by events or invoke?

Yes, sessions now propagate automatically to any run triggered by another run, whether through an event, invoke, or defer. Setting a session once on the root run causes the entire resulting run tree to be grouped together on the Sessions page, which is useful when a single action fans out into multiple functions, as is common with AI agents.

_Teams tracing multi-function AI agent runs can follow session propagation updates like this on daily.dev._

### What information does the Inngest Sessions page show for a session?

The Sessions page shows run counts, failures, recent activity, and the functions involved for each session. With propagation, this view now covers an entire tree of child runs spawned from a single root run, making it easier to monitor long-running workflows and agent fan-out from one place.

_Debugging fan-out workflows gets easier when you track platform changes like this via daily.dev._

## Similar posts on daily.dev

- [Session Traces and Cost Controls Help Diagnose AI Agent Failures](https://daily.dev/posts/session-traces-and-cost-controls-help-diagnose-ai-agent-failures-cphogfesa) · InfoQ · 0 upvotes · 0 comments
- [AWS, Microsoft and Google agree the session is the new unit. They disagree on how to isolate it.](https://daily.dev/posts/aws-microsoft-and-google-agree-the-session-is-the-new-unit-they-disagree-on-how-to-isolate-it--fyff0nkhp) · The New Stack · 0 upvotes · 0 comments
- [Introducing My agent sessions, one view for all your agent activity](https://daily.dev/posts/introducing-my-agent-sessions-one-view-for-all-your-agent-activity-lac4ooo2t) · Atlassian · 1 upvotes · 0 comments
- [Investigate user sessions end-to-end with the new Session Replay](https://daily.dev/posts/investigate-user-sessions-end-to-end-with-the-new-session-replay-y4m6yq89n) · Dynatrace · 1 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#inngest](https://daily.dev/tags/inngest), [#observability](https://daily.dev/tags/observability), [#workflow-orchestration](https://daily.dev/tags/workflow-orchestration)

[View this post on daily.dev](https://daily.dev/posts/propagated-sessions-oegd4csaa)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Propagated Sessions","url":"https://daily.dev/posts/propagated-sessions-oegd4csaa","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/propagated-sessions-oegd4csaa"},"datePublished":"2026-09-13T19:57:26.363Z","dateModified":"2026-10-15T02:22:33.033Z","description":"Inngest sessions now propagate automatically to child runs triggered by events, invokes, or defers, so a whole run tree started from one root run is grouped...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d45b5c80b6cea1c5a8a78e9609c02fd3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d45b5c80b6cea1c5a8a78e9609c02fd3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Inngest Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Inngest Blog","logo":"https://media.daily.dev/image/upload/s--ieZKUa5y--/c_limit,w_256/f_auto,q_auto/v1789329423/logos/inngest?_a=BAMAMicg0","url":"https://daily.dev/sources/inngest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/propagated-sessions-oegd4csaa","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,inngest,observability,workflow-orchestration","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Inngest Blog","item":"https://daily.dev/sources/inngest"},{"@type":"ListItem","position":3,"name":"Propagated Sessions"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/propagated-sessions-oegd4csaa#faq","mainEntity":[{"@type":"Question","name":"Do Inngest sessions propagate to child runs triggered by events or invoke?","acceptedAnswer":{"@type":"Answer","text":"Yes, sessions now propagate automatically to any run triggered by another run, whether through an event, invoke, or defer. Setting a session once on the root run causes the entire resulting run tree to be grouped together on the Sessions page, which is useful when a single action fans out into multiple functions, as is common with AI agents. Teams tracing multi-function AI agent runs can follow session propagation updates like this on daily.dev."}},{"@type":"Question","name":"What information does the Inngest Sessions page show for a session?","acceptedAnswer":{"@type":"Answer","text":"The Sessions page shows run counts, failures, recent activity, and the functions involved for each session. With propagation, this view now covers an entire tree of child runs spawned from a single root run, making it easier to monitor long-running workflows and agent fan-out from one place. Debugging fan-out workflows gets easier when you track platform changes like this via daily.dev."}}]}
```

