fix(exa): revert conditional required on Get Contents URLs

The conditional required callback did not work and introduced a
regression. `isFieldRequired` in webhook deploy calls `config.required()`
with no arguments, so the callback never saw `ids` and left URLs required
— an ids-only block would have been reported as missing a required field
on deploy. `collectBlockFieldIssues` skips sub-block required checks
whose id matches a tool param, so it never evaluated the callback either.

Both selectors go back to optional with the exactly-one check in the
request body, which is what the integration rules prescribe for mutually
exclusive alternate identifiers. Added a comment recording why a
conditional required cannot express this, so it is not reattempted.

Author: waleedlatif1

apps/sim/blocks/blocks/exa.ts

@@ -22,11 +22,6 @@ const CATEGORY_OPTIONS = [
  * carrying a stored research query forward — it drops any value whose sub-block
  * condition no longer matches.
  */
-/** True when a sub-block holds a non-empty user value. */
-function hasValue(value: unknown): boolean {
-  return typeof value === 'string' ? value.trim().length > 0 : value != null
-}
-
 const LEGACY_RESEARCH_OPERATION = 'exa_research'
 const AGENT_OPERATIONS = ['exa_agent', LEGACY_RESEARCH_OPERATION]
 
@@ -270,17 +265,6 @@ export const ExaBlock: BlockConfig<ExaResponse> = {
       placeholder: 'Enter URLs to retrieve content from (comma-separated)...',
       description: 'Provide either URLs or Result IDs, not both',
       condition: { field: 'operation', value: 'exa_get_contents' },
-      /**
-       * Exactly one selector is needed. Inverting the operation match when
-       * Result IDs are present makes the requirement fall away for this
-       * operation, so the editor flags an empty config without blocking the
-       * ids-only path.
-       */
-      required: (values) => ({
-        field: 'operation',
-        value: 'exa_get_contents',
-        not: hasValue(values?.ids),
-      }),
     },
     {
       id: 'ids',
@@ -291,6 +275,14 @@ export const ExaBlock: BlockConfig<ExaResponse> = {
       condition: { field: 'operation', value: 'exa_get_contents' },
       mode: 'advanced',
     },
+    /*
+     * URLs and Result IDs are mutually exclusive alternate identifiers, so both
+     * stay optional and the request body enforces exactly one. A conditional
+     * `required` cannot express this: `isFieldRequired` in webhook deploy calls
+     * the callback with no arguments, so it would mark URLs missing on a valid
+     * ids-only block, and `collectBlockFieldIssues` skips sub-block required
+     * checks whose id matches a tool param, so it would never run there anyway.
+     */
     {
       id: 'text',
       title: 'Include Text',

apps/sim/tools/exa/exa.test.ts

@@ -185,14 +185,13 @@ describe('exa block', () => {
     expect(params.effort).toBe('medium')
   })
 
-  it('requires URLs on Get Contents when no result IDs are supplied', () => {
-    const urls = ExaBlock.subBlocks.find(
-      (block) => block.id === 'urls' && block.condition?.value === 'exa_get_contents'
-    )
-    const required = urls?.required as (values?: Record<string, unknown>) => { not?: boolean }
-    expect(required({}).not).toBe(false)
-    expect(required({ ids: '   ' }).not).toBe(false)
-    expect(required({ ids: 'id-1' }).not).toBe(true)
+  it('leaves both Get Contents selectors optional so the ids-only path stays valid', () => {
+    for (const id of ['urls', 'ids']) {
+      const selector = ExaBlock.subBlocks.find(
+        (block) => block.id === id && block.condition?.value === 'exa_get_contents'
+      )
+      expect(selector?.required).toBeUndefined()
+    }
   })
 
   it('keeps the legacy model sub-block so the serializer preserves its value', () => {