Skip to content

docs: add workflow_run_id and workflow_recipient_run_id fields to Messages table structure #1018

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

devin-ai-integration[bot]
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Jul 7, 2025

Add workflow_run_id and workflow_recipient_run_id fields to Messages table structure

Summary

This PR adds two new fields to the Messages table structure in the Data warehouse sync documentation:

  • workflow_run_id: Unique identifier for the top-level workflow run that generated this message
  • workflow_recipient_run_id: Unique identifier for the individual recipient run within the workflow

The changes follow the same format as the recently added guide_id and guide_key fields from PR #947, maintaining consistency with the existing table structure documentation.

Review & Testing Checklist for Human

  • Verify field descriptions are accurate - Confirm the descriptions for workflow_run_id and workflow_recipient_run_id correctly reflect what these fields contain based on the actual data model
  • Check SQL example consistency - Determine if the SQL CREATE TABLE example should also be updated to include these fields (note: guide_id and guide_key are also missing from the SQL example)
  • Test documentation rendering - Verify the table formatting displays correctly when the docs are built and deployed
  • Confirm field placement - Ensure the new fields are positioned appropriately in the table structure (currently placed after guide fields)

Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    DataSync["data-sync.mdx<br/>Data warehouse sync docs"]:::major-edit
    MessagesTable["Messages table structure<br/>Table component"]:::major-edit
    SQLExample["SQL CREATE TABLE example<br/>Accordion section"]:::context
    GuideFields["guide_id, guide_key<br/>Existing similar fields"]:::context
    
    DataSync --> MessagesTable
    DataSync --> SQLExample
    MessagesTable --> GuideFields
    
    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit
        L3[Context/No Edit]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB
    classDef context fill:#FFFFFF
Loading

Notes

Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link

vercel bot commented Jul 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 7, 2025 8:02am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant