Hacker News new | past | comments | ask | show | jobs | submit login

Hey, I’m building agents on top of temporal as well. One of the main limitations is child workflows can not spawn other child workflows. Are you doing an activity for every prompt execution and passing those through other activities? Or something more framework-y?



Right now I'm doing prompt execution in activities, passing results to other activities.

Workflows currently only started after human events, but going to move towards additional workflows started through an activity soon - I'm keeping the state of the world independent of the execution engine so each workflow will read the new state.


Have you hit any non-determinism errors keeping workflow state outside temporal?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: