Way to fire and forget the tool call

[daneatmastra]

This issue was created from Discord post 1442460770607824981:

Hi team, wanted to know if there is a way to fire and forget the tool calls. We can do this with tools that we design but say for tool like updateWorkingMemory it slows down the whole workflow. Is there a way to fire and forget?

[daneatmastra]

Thank you for reporting this issue! We have assigned it to the trio-tnt and we will look into it as soon as possible.

If you're experiencing an error, please provide a minimal reproducible example whenever possible to help us resolve it quickly.

[daneatmastra]

Discord Message from souvikinator at 2025-11-24T10:24:07.338Z

Hi team, wanted to know if there is a way to fire and forget the tool calls. We can do this with tools that we design but say for tool like updateWorkingMemory it slows down the whole workflow. Is there a way to fire and forget?

View in Discord

---

This message was automatically synced from Discord

[daneatmastra]

Discord Message from graysonatmastra at 2025-11-24T14:47:16.672Z

Hey <@761238725542936596> ! I don't think there is a built-in 'fire and forget' API, but if you have multiple independent tools that don't depend on each other, you can use .parallel() in workflows to execute them concurrently:

const step1 = createStep({
  id: "step-1",
  execute: async () => {
    // Some operation
  }
});

const step2 = createStep({
  id: "step-2", 
  execute: async () => {
    // updateWorkingMemory or other tool
  }
});

  const workflow = createWorkflow({...})
    .parallel([step1, step2])  // Both run concurrently
    .commit();

    const step1 = createStep({  id: "step-1",  execute: async () => {    
    // Some operation  
    }});
    const step2 = createStep({  id: "step-2",   execute: async () => {    
    // updateWorkingMemory or other tool  
    }});

  const workflow = createWorkflow({...})
    .parallel([step1, step2])  // Both run concurrently  
    .commit();

View in Discord

---

This message was automatically synced from Discord

[daneatmastra]

Discord Message from graysonatmastra at 2025-11-24T14:50:06.432Z

Alternatively (but I think less desirable) within a step's execute function, you could trigger an async operation without awaiting it:

const step = createStep({  execute: async ({ inputData }) => {    
// Fire and forget - don't await    
Promise.resolve().then(async () => {      
    await updateWorkingMemory(...);    
  }).catch(error => {      
    // Handle errors appropriately      
    console.error('Background operation failed:', error);    });        
   // Continue immediately with the main flow    
  return { result: "continued without waiting" }; 
 }});

⚠️ Warning: This approach has trade-offs:
No guarantee the operation completes
Errors may not be properly handled
Memory operations may not persist before workflow completion

View in Discord

---

This message was automatically synced from Discord

[daneatmastra]

Discord Message from graysonatmastra at 2025-11-24T14:50:23.006Z

Definitely open to API feedback if the parallel solution isn't a good fit!

View in Discord

---

This message was automatically synced from Discord

[daneatmastra]

Discord Message from abhiaiyer_14031 at 2025-11-24T15:24:50.040Z

updateWorkingMemory is auto executed by an Agent, it doesn't fire and forget though. I'm not sure it's a good idea to do so cause we need the operations to complete to correctly update working memory.

<@761238725542936596> what's your agent setup look like ?

View in Discord

---

This message was automatically synced from Discord

[daneatmastra]

Discord Sync Tracker

• Last Message ID: 1442536447184994395
• Last Sync Timestamp: 2025-11-24T22:45:17.096Z
• Last Author is Team Member: Yes

---

This tracker helps prevent duplicate message syncing from Discord