Troubleshooting

Use this guide to distinguish configuration problems, expected provider behavior, dataset availability issues, and calculation states.

Provider controls are unavailable

Venue, Symbol, and Timeframe choices depend on Provider metadata. If they are disabled or empty:

1. Open Providers and select the configuration.
2. Check its readiness or validation message.
3. Confirm required credentials for an account-backed Provider.
4. Retry metadata loading when the Provider or network was temporarily unavailable.
5. Confirm the requested market belongs to the Provider’s supported current scope.

Binance Global Spot intentionally omits authentication, tier, Usage Estimate, and redundant Venue controls. Their absence is not a loading failure.

A Job cannot start

Check Draft validation in this order:

1. Provider readiness.
2. Symbol and Timeframe selection.
3. Mode and UTC History range.
4. Indicator Set validity and plan limit.
5. Dataset folder access.
6. Dataset size-limit configuration.
7. Subscription capability for the selected workflow.

Dismissing a Paywall does not make a blocked configuration valid.

History is at 100% but the Job is not complete

Historical loading and provider finality are separate. 100.0% means the requested fetch/write phase reached its full range. Awaiting final bars means recent periods still have provider confirmation work.

Wait for the provider-specific due time and confirmation. Do not interpret the progress percentage as a guarantee that every recent row is already final.

The dataset contains missing OHLCV cells

Inspect bars.provider_data_status and the matching gaps history.

1. pending_finalization can still receive or revise provider data.
2. provider_omitted means the provider returned no row after the applicable check.
3. provider_error identifies a localized request/data failure.

DataCat keeps raw cells NULL rather than filling them with invented OHLCV. This is intentional and makes missing input visible.

A provider omitted a period

An absent row does not prove that no trades occurred. Providers differ in empty-period behavior, and DataCat does not query a separate trades endpoint to infer a no-trade classification in the current release.

Ordinary omission may be terminal and non-alarming for one Provider. Use the persisted provider state and your own downstream policy rather than assuming every omission is a service outage.

Indicator values are NULL

Read the effective output state in indicator_output_states_json:

1. warmup: the instance needs more usable history.
2. awaiting_input: leading pending input has no prior usable close.
3. unavailable: required input cannot be used.

If the row is provisional or derived, a numeric value can exist but still depend on non-final or calculation-normalized input.

Indicator values differ from another platform

Verify the exact provider, venue, symbol, timeframe, UTC range, parameter values, input columns, warmup, and missing-period policy. Two tools can use the same indicator name with different defaults or data.

Use indicator_definitions to inspect the frozen DataCat instance and its resolved parameters. Compare final rows before investigating numerical divergence.

Dataset missing

DataCat cannot locate the expected dataset artifact. Check whether the folder or database was moved, renamed, deleted, or disconnected.

The current product does not provide a general Dataset Relink workflow. Preserve external copies, but do not expect moving a dataset behind an active Job to update app state automatically.

Dataset access

The dataset exists but DataCat cannot currently access it. Check folder permissions, external-volume availability, security-scoped access, and whether another operation replaced part of the artifact.

Do not repair the problem by editing DataCat tables manually.

Size limit reached

DataCat stops before writing the next bar when the dataset reaches its configured limit. Use Continue in New Job to create a new dataset and preserve lineage.

Changing the global default applies to new Jobs only; it does not retroactively enlarge an existing Job’s captured limit.

Live data appears delayed

Separate these possibilities:

1. The current period is still open and is not yet a completed bar.
2. The provider WebSocket is healthy but the market has no eligible event.
3. DataCat is using REST fallback during recoverable WebSocket disruption.
4. A completed row is written but remains pending provider finality.
5. Provider rate limits or network backoff are delaying confirmation work.

The REST finality delay does not intentionally delay primary WebSocket Live delivery.

Preparing a support request

Include:

1. DataCat version and build.
2. macOS version.
3. Provider family, Job mode, Symbol, Timeframe, and approximate UTC time range.
4. Job ShortID or other non-secret user-facing context.
5. The visible error title and detail.
6. Reproduction steps and whether the issue persists after reopening DataCat.

Do not include API keys, JWT secrets, authentication headers, Keychain values, full provider payloads, raw dataset contents, private file paths, or unrelated personal data. Use Send Feedback or the published support address according to the sensitivity of the issue.