FAQ

FAQ

chevron-rightDo I need to provide IDs for every event?hashtag
  • Sequential thinking: Optional, backend can generate, but still recommended to provide

  • Parallel thinking: Required, backend cannot generate correct IDs for parallel thinking

  • Activities: Optional, but recommended for tracking

chevron-rightWhat happens if I don’t provide a message for activities?hashtag
  • Backend will auto-generate a message:

  • With types field available: Type-specific message

  • Not provide any types: Markdown-formatted list of fields

chevron-rightCan I emit thinking events without start/end markers?hashtag

No, you must follow the sequence: thinking_start → thinking → thinking_end

chevron-rightCan I reuse the same ID for different thinking streams?hashtag

Yes, but only if streams are sequential (one finishes before next starts). For parallel streams, use different IDs.

chevron-rightHow do I know if my events are being processed correctly?hashtag

Check the database messages.metadata_["events"] field after pipeline completes. Events should be stored with proper structure and merged thinking streams.


Last updated