Stock research that survives a closed browser

Prerequisites

• A free Render account
• Submit the Render Atlanta workshop form so you can be added to the shared workspace
• A GitHub account
• Git and Node.js 20+ on your machine
• Comfortable editing TypeScript in a local IDE and using the Render Dashboard

Steps

1. 01 Join the Render workspace Submit the Render Atlanta workshop form so we can add you to the shared Render workspace. 3 min →
2. 02 What you'll build See why long-running research stuck inside one HTTP request is hard to resume, then wrap those steps as Workflow tasks with one root task-run ID you can look up later. 3 min →
3. 03 Deploy the starter Check prerequisites, fork the starter, understand the multi-step request-owned pipeline, and deploy a live web service. 6 min →
4. 04 Feel the broken run On your live URL, start research, close the tab mid-run, and confirm there is nothing to recover. 5 min →
5. 05 Add Workflows in your IDE Clone your fork, register the research steps as Workflow tasks (one root, several step tasks), and change the web API so it returns a root task-run ID. 10 min →
6. 06 Create and test the Workflow Create a Workflow service from your fork, confirm several tasks are registered, run the root researchStock once from the Dashboard, and confirm POST returns a task-run ID. 7 min →
7. 07 Recover and verify Prove the close-tab experiment recovers both the memo and the live tracker from the stored root task-run ID. 4 min →