# Bidding Input Files

Place Excel input files for IDAS bidding here.

- `single_bid/` for normal single-bid templates
- `block_bid/` for future block-bid templates
- `json/` for direct structured bid payloads
- `uploads/` for files sent through the application's `Upload` flow
- `folder_uploads/` for folder-upload scenarios grouped by market, screen, side, and TM ID

For folder uploads, `folder_upload_sides` can be set to `Buy`, `Sell`, or `BUYSELL`.
`BUYSELL` uses a `BUYSELL` side folder when it exists; otherwise it runs the `Buy`
and `Sell` side folders for the selected market and screen.

Large folder uploads can take longer than normal grid entry. The regression config
uses `folder_upload_progress_timeout_seconds` for the maximum upload wait and
`folder_upload_keep_alive_interval_seconds` for periodic browser activity during
that wait.
If `folder_upload_continue_when_last_file_complete` is true, the runner can
continue when the last uploaded file reaches 100%, even if earlier rows remain
below 100% because of errors such as bid-data validation. Incomplete rows are
logged with file name, progress, and remarks.

Folder uploads run sequentially by default. Set `folder_upload_execution_mode` to
`parallel` to run multiple TM folders at the same time, using
`folder_upload_max_parallel_sessions` to control the number of browsers and
`folder_upload_parallel_login_stagger_seconds` to stagger manual CAPTCHA entry.
Use `folder_upload_parallel_captcha_wait_seconds` to control how long each
parallel browser waits before submitting login after you type the CAPTCHA.
Parallel mode uses one login per browser slot. With exchange login it uses
`users.exchange_parallel`. With trading-member login it uses the entries under
`users.trading_members`, and each member must list the TM folders it can upload
with `folder_upload_tm_ids` or a matching `member_id`. Trading-member runs skip
the TM dropdown because the application locks the TM to the logged-in user.

Config can now choose one of these bid-entry methods:

- `excel_grid`
- `json_grid`
- `file_upload`
- `folder_upload`

For block-bid bulk upload, set `active_selection.bidding_screen` to `block_bid`
and choose `IDAS > bidding > entry_method > block_bid > block_upload_method` as
`file_upload` or `folder_upload`. Folder upload uses the same grouped directory
shape, with `Block` instead of `Single`, for example:

```text
data/idas/bidding/folder_uploads/DAM/Block/BUYSELL/C1032
```

Set `active_selection.bidding_screen` to `single_and_block_bid` to run both
folder-upload screens in one browser login. The runner processes `single_bid`
first, then navigates directly to block bulk upload for `block_bid`.

After the block folder is selected, the runner accepts the browser upload
confirmation when WebDriver exposes it, then waits until the page success message
changes to `FOLDER_UPLOADED_SUCCESSFULLY`. Timing is logged from file selection
through the success message. For large load-test folders, tune
`block_upload_success_timeout_seconds`, `block_upload_success_poll_seconds`, and
`block_upload_progress_log_interval_seconds` in `runtime.json`.