# Exa Websets Polling Blocks for polling and waiting on Exa webset operations to complete. ## Exa Wait For Enrichment ### What it is Wait for a webset enrichment to complete with progress tracking ### How it works This block polls an enrichment operation until it completes or times out. It checks status at configurable intervals and can include sample results when done. Use this to block workflow execution until enrichments finish, enabling sequential operations that depend on enrichment data being available. ### Inputs | Input | Description | Type | Required | | --------------- | ------------------------------------------------- | ---- | -------- | | webset\_id | The ID or external ID of the Webset | str | Yes | | enrichment\_id | The ID of the enrichment to monitor | str | Yes | | timeout | Maximum time to wait in seconds | int | No | | check\_interval | Initial interval between status checks in seconds | int | No | | sample\_results | Include sample enrichment results in output | bool | No | ### Outputs | Output | Description | Type | | ----------------- | -------------------------------------- | ---------------------------- | | error | Error message if the operation failed | str | | enrichment\_id | The enrichment ID that was monitored | str | | final\_status | The final status of the enrichment | str | | items\_enriched | Number of items successfully enriched | int | | enrichment\_title | Title/description of the enrichment | str | | elapsed\_time | Total time elapsed in seconds | float | | sample\_data | Sample of enriched data (if requested) | List\[SampleEnrichmentModel] | | timed\_out | Whether the operation timed out | bool | ### Possible use case **Sequential Processing**: Wait for enrichments to complete before proceeding to export or analysis. **Data Validation**: Ensure enrichments finish and review samples before continuing workflow. **Synchronous Workflows**: Convert async enrichment operations to blocking calls for simpler logic. *** ## Exa Wait For Search ### What it is Wait for a specific webset search to complete with progress tracking ### How it works This block polls a webset search operation until it completes or times out. It provides progress information including items found, items analyzed, and completion percentage. Use this when you need search results before proceeding with downstream operations like enrichments or exports. ### Inputs | Input | Description | Type | Required | | --------------- | ------------------------------------------------- | ---- | -------- | | webset\_id | The ID or external ID of the Webset | str | Yes | | search\_id | The ID of the search to monitor | str | Yes | | timeout | Maximum time to wait in seconds | int | No | | check\_interval | Initial interval between status checks in seconds | int | No | ### Outputs | Output | Description | Type | | ---------------------- | ------------------------------------------------- | --------------- | | error | Error message if the operation failed | str | | search\_id | The search ID that was monitored | str | | final\_status | The final status of the search | str | | items\_found | Number of items found by the search | int | | items\_analyzed | Number of items analyzed | int | | completion\_percentage | Completion percentage (0-100) | int | | elapsed\_time | Total time elapsed in seconds | float | | recall\_info | Information about expected results and confidence | Dict\[str, Any] | | timed\_out | Whether the operation timed out | bool | ### Possible use case **Search Completion**: Wait for initial webset population before accessing items. **Progress Monitoring**: Track search progress in long-running operations. **Sequential Workflows**: Ensure searches complete before starting enrichments. *** ## Exa Wait For Webset ### What it is Wait for a webset to reach a specific status with progress tracking ### How it works This block polls a webset until it reaches a target status (idle, completed, or running). It uses exponential backoff for efficient polling and provides detailed progress information. Use this for general-purpose waiting on webset operations when you don't need to track a specific search or enrichment. ### Inputs | Input | Description | Type | Required | | ----------------- | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | -------- | | webset\_id | The ID or external ID of the Webset to monitor | str | Yes | | target\_status | Status to wait for (idle=all operations complete, completed=search done, running=actively processing) | "idle" \| "completed" \| "running" \| "paused" \| "any\_complete" | No | | timeout | Maximum time to wait in seconds | int | No | | check\_interval | Initial interval between status checks in seconds | int | No | | max\_interval | Maximum interval between checks (for exponential backoff) | int | No | | include\_progress | Include detailed progress information in output | bool | No | ### Outputs | Output | Description | Type | | -------------------- | ---------------------------------------- | --------------- | | error | Error message if the operation failed | str | | webset\_id | The webset ID that was monitored | str | | final\_status | The final status of the webset | str | | elapsed\_time | Total time elapsed in seconds | float | | item\_count | Number of items found | int | | search\_progress | Detailed search progress information | Dict\[str, Any] | | enrichment\_progress | Detailed enrichment progress information | Dict\[str, Any] | | timed\_out | Whether the operation timed out | bool | ### Possible use case **Workflow Orchestration**: Wait for all webset operations to complete before next workflow steps. **Idle State Detection**: Ensure webset is fully idle before making configuration changes. **Completion Gates**: Block workflow until webset reaches a specific readiness state. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://agpt.co/docs/integrations/block-integrations/websets_polling.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.