# rfp agent browser automation failed on jaggaer rfp package download: how to fix it

Browser automation often clicks download but never waits for the file. Configure the download directory, click, then wait for the file to appear with a stable size before continuing.

```text
rfp agent browser automation failed on jaggaer rfp package download
```

## When to use this skill
- Agent clicks download but no file appears
- Download starts but the agent moves on too early

## When not to use this skill
- Download 403s (a permissions issue)
- Package downloads but is corrupt (an integrity issue)

## Tool compatibility
Agent Jaggaer package download. Related area: browser automation.

Related area: proposal automation and agent-assisted RFP workflows.

Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with agent clicks download but no file appears, start at step 1 below.
- If instead download 403s (a permissions issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Set the download directory

```
Configure the browser to download files to a known folder without prompting.
```
Expected: Expected: no save dialog appears.

### 2. Click the package download

```
Click the RFP package download link.
```
Expected: Expected: download starts.

### 3. Wait for a stable file

```
Poll the download folder until the file stops growing.
```
Expected: Expected: complete file on disk.

### 4. Verify the package

```
Check the file size against the listing and open it.
```
Expected: Expected: package opens with all documents.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (set the download directory): Expected: expected: no save dialog appears.
- Step 2 (click the package download): Expected: expected: download starts.
- Step 3 (wait for a stable file): Expected: expected: complete file on disk.
- Step 4 (verify the package): Expected: expected: package opens with all documents.

## Quick recap
1. Set the download directory
2. Click the package download
3. Wait for a stable file
4. Verify the package

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### agent jaggaer download failed
Wait for a stable file. If this matches what you saw, the steps above apply as written.

### agent rfp package download browser
Download directory config is required. If this matches what you saw, the steps above apply as written.

## Why it happens
Automated browsers default to prompting for downloads, which stalls headless runs, and agents that do not wait for completion process partial files. Explicit download config plus a stable-size wait covers both.

## Edge cases
- Disable download prompts in the browser profile before the run
- Large packages take minutes; size the wait budget accordingly
- Verify the package manifest against the downloaded files

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fhTbX26n5HiP6icq5WlqlA