fix(backend): Re-work the connection input consumption logic for Agent Executor Block

[majdyz]

Agent Executor Block puts all the data within the data field of the input. And the rest of the input is metadata. The current implementation only validates the input of block input (which is the metadata), but not validating the data value against the schema of the graph.

This makes the graph always executed once there is a trigger input, without waiting the inbound connection data and uses the default value.

Issue Repro:

• Create an agent with > 1 input, and set the default value on each.
• Re-use that agent as a block, and provide the input value from another node as opposed to the default value.
• Run the agent.
• Before this change: one of the inputs will use the default value instead of a provided node from the inbound links.

Changes 🏗️

Add a graph input schema validation to the graph to force the execution to wait for all the connecting input fields are completed and provided.

Checklist 📋

For code changes:

• [ ] I have clearly listed my changes in the PR description
• [ ] I have made a test plan
• [ ] I have tested my changes according to the test plan:
  • [ ] ...

Example test plan

- [ ] Create from scratch and execute an agent with at least 3 blocks - [ ] Import an agent from file upload, and confirm it executes correctly - [ ] Upload agent to marketplace - [ ] Import an agent from marketplace and confirm it executes correctly - [ ] Edit an agent from monitor, and confirm it executes correctly

For configuration changes:

• [ ] .env.example is updated or already compatible with my changes
• [ ] docker-compose.yml is updated or already compatible with my changes
• [ ] I have included a list of my configuration changes in the PR description (under Changes)

Examples of configuration changes

- Changing ports - Adding new services that need to communicate with each other - Secrets or environment variable changes - New or infrastructure changes such as databases

[codiumai-pr-agent-pro[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The error handling in validate_exec() function could be improved. The function returns None and error message in multiple places but the error messages have inconsistent formats and prefixes. Code Duplication The validation logic for required fields and schema validation is duplicated between the AgentExecutorBlock case and the regular case. Consider extracting common validation logic into a helper function. Type Safety The type conversion in the non-AgentExecutorBlock case assumes the conversion will always succeed. Should add error handling around the convert() function call.

[netlify[bot]]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	6378beadb364afac387829a4ee282887a83715a4
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/673f12d5cc13ac0008596364

[Torantulino]

Working on my end!

[majdyz]

@Pwuts addressed your comment, pls re-review 🙏