> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/market-replay-docs/reference/errors-and-troubleshooting.md).

# Errors and troubleshooting

Fix the most common Market Replay request issues fast.

Use this page when a request fails or returns data you did not expect.

## Authentication errors

### Invalid username or password

Check these first:

* the username is correct
* the password is correct
* the account is enabled for the endpoint

If credentials include reserved characters, URL-encode them.

Examples:

* space becomes `%20`
* `+` becomes `%2B`
* `&` becomes `%26`

### One endpoint works and another fails

Access can vary by dataset.

Confirm your account is enabled for the endpoint you are calling.

## Empty or incomplete results

### Tick query spans more than one day

Tick queries return data for one day only.

Run one request per day for multi-day downloads.

### `end` looks inclusive

`end` is exclusive.

Move `end` forward if you need the last expected record included.

### Fewer rows than expected with `maxrecords`

The result depends on the time range, sort order, and data availability.

For tick queries, all ticks in the matching second are returned even if that exceeds the requested limit.

## Time and symbol issues

### Wrong time zone

Use:

* Eastern Time for equities
* Central Time for futures and most other markets

### Wrong symbol format

Check the symbol type:

* equities use symbols like `AAPL`
* futures may use root notation like `ES*1`
* futures options EOD uses `root` and `date`, not `symbol`

### No data for the requested range

Check the available range first:

* `queryminutedaterange.ashx`
* `queryeoddaterange.ashx`

## Response parsing issues

### CSV shape is different than expected

Different endpoints return different columns.

Verify the response format before parsing:

* ticks include timestamp, trading day, and trade or quote fields
* minutes include OHLCV
* EOD includes symbol, date, OHLCV, and sometimes open interest

### Futures options returns JSON or CSV

Use:

* `futuresoptions` for CSV
* `futuresoptions/json` for JSON

## Quick checks

Before debugging deeper, confirm:

* the base URL matches the endpoint
* the query string uses the right parameter names
* `start` and `end` use the right format
* the account has access to the dataset

## Related

* [Authentication](/market-replay-docs/reference/authentication.md)
* [Query parameter cheat sheet](/market-replay-docs/reference/query-parameter-cheat-sheet.md)
* [curl examples](/market-replay-docs/getting-started/curl-examples.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.barchart.com/market-replay-docs/reference/errors-and-troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.