Re: Workflows and storing information in context vs sending it via event class parameters

[sumitbindra]

I am a little confused about this in the workflows:

(1) is there a reason to not store every piece of information in context instead of sending it via an event class parameter?
(2) If I dont want to send any information with event class parameter, can i have an empty class or should I always find something to send always (like status = "success")?

Thanks.

Sumit

[dosubot[bot]]

1. Storing every piece of information in context is not always ideal. The context is best used for data that needs to be shared across non-connected steps or for managing global state, especially when dealing with large data operations. Using context for all data can lead to unnecessary complexity and potential performance issues due to the overhead of managing global state ^[1][2].

2. You can indeed use an empty event class if you don't need to send any information via event class parameters. The LlamaIndex framework has examples of empty event classes, such as LLMEmptyResponseEvent, which are handled appropriately without additional data ^[3][4].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}