Chart analysis still running? Check its status before trying again

If a ChartPilot analysis is still running, check whether the request was accepted, whether progress is available, and whether a saved result is ready before submitting the image again. A connection interruption can stop your browser from receiving an update without establishing that the analysis itself failed.

This guide follows the current analyzer’s visible states. If you are preparing your first review, review current ChartPilot signup options. New accounts require a payment method for a seven-day Premium trial, then renew at $59 USD/month unless canceled before trial end; applicable taxes appear at checkout. There is no ongoing free plan for new accounts. Existing free accounts retain their allowance under the current terms.

First, distinguish submitting from accepted

After selecting Analyze chart, the analyzer can show Submitting your chart… and ask you to wait for acceptance before leaving. That is a different stage from an accepted chart waiting in the queue or being reviewed. Selecting an image, seeing its preview and pressing the action are not, by themselves, confirmation of acceptance.

In the member workspace, the progress steps identify submission, evidence review and saving the result. Look for Accepted under the submission step or a queued or reviewing state before treating the request as accepted. If the page instead reports that the request could not be confirmed, its outcome is still unresolved.

Once accepted, the interface says you can leave and return. The public FAQ also describes returning to the analyzer for progress or a saved result, with one analysis running at a time. Keep that acceptance boundary in mind if you switch apps on a phone or close a tab.

Use the message to choose the next check

The wording can vary with the stage and workspace view. An elapsed timer is a record of waiting time, not proof of completion or failure. If you cannot establish the current state, write “unknown” instead of deciding that the request disappeared.

When the connection breaks, check the existing request

The analyzer can show Connection interrupted. Check analysis status below before retrying. The error area provides Check analysis status when you are signed in. During an accepted analysis, a reconnection message can also offer Check now. These controls ask for the existing analysis status; they are not instructions to start another assessment.

Restore your connection, return to the analyzer with the same account and inspect what it shows. If account information cannot be verified, the interface may offer Refresh account. Resolve that account check before interpreting a missing result as an analysis failure.

Do not treat closing or refreshing the page as a cancellation command. The accepted request continues independently of the progress view. Equally, a failed attempt to check status cannot tell you whether the work has completed in the meantime. Use the next successful status response or the saved result to resolve that uncertainty.

If it takes longer than expected

The homepage asks users to allow up to four minutes. Use that guidance to plan your review, not as proof that a request failed at a particular second. The member workspace has a Your chart is still being reviewed. state for a longer-running analysis.

Read any connection message, check status using the available control, or return later. Repeatedly pressing Analyze chart does not explain the delay. If the state remains unresolved, record the time and exact message before seeking help through the published support contact.

A useful support note identifies the instrument, timeframe, approximate submission time with timezone, last visible state and what changed after checking again. Include only the details needed to investigate; do not send passwords, card information or an unredacted account screen.

A fictional interrupted-connection example

Illustrative scenario, not an actual customer incident: at 09:10, a user submits a 15-minute EURUSD screenshot and sees Accepted. At 09:11, the browser loses its connection while the user switches apps. The missing update does not establish a failed analysis.

After reconnecting, the user returns with the same account and checks progress. In one possible outcome, the original request is still running. In another, the result is ready and can be opened. A third possibility is an explicit failure requiring attention. The useful action is to identify which outcome occurred, not to assume one from the interruption alone.

If the connection had broken while the screen still said Submitting, acceptance would also be unknown. Checking the existing request and history comes before deciding whether a fresh submission is needed. This distinction prevents an uncertain browser response from becoming an unsupported conclusion about the server.

Open the matching result, then resume the review

A completed assessment may appear directly, or a ready notice may provide Open result while you browse history. Match its instrument, timeframe and recorded date to the review you intended. A previously saved assessment or sample is not evidence that this particular request completed.

If the interface reports an unreadable image, use the screenshot troubleshooting guide. If it reports a technical failure, follow that message and retry only after the previous outcome is known and the interface permits a new request. Do not infer remaining allowance from a spinner or an interrupted connection; use your account’s displayed access and current terms.

Once the correct result is open, the history and review-journal guide helps you record what you checked. The assessment still concerns the submitted screenshot; it does not become a live quote because you opened it later.

Review current signup options when you are ready to begin. For an existing request, finish with one confirmed outcome: still active, completed and opened, or an explicit problem with a clear next step.