Skip to content
Interface language: English
Design / Signal

Still working: progress, cancellation and returning to a long-running task

Explain progress, cancellation and return paths so people can understand a long-running task and collect its result.

Article language: English

A woman holding a fan beneath red fabric beside a stream of water.
In this article

A package of materials is 97 percent ready. For the next few minutes nothing changes. The user has had time to read every file name, check their email and develop a personal relationship with the remaining three percent. What they do not know is whether they can close the tab and return later.

For a long-running task, progress information should help someone decide whether to wait, do something else, stop the work or collect the result. A moving indicator is only one part. The design must explain the task's state and available actions, including after a connection is lost and the person returns to the service.

In the fictional Barwa studio dashboard, a customer selects materials for a larger package. The service prepares an archive of drawings and photographs. The result is not immediate, and preparation may take longer than the person spends on the page. Let us arrange the journey from request to file retrieval without guessing what the back end does.

The task state should lead to a decision

First establish what accepting a request means. Clicking a button does not necessarily mean the task was saved and sent for execution. The screen should distinguish sending a request, confirmed acceptance and work that has started when there is a perceptible gap between them. The text must reflect signals the system actually provides.

In Barwa, the task view should show what the package contains, when it was requested and where to check the result. “Processing” alone will not help someone returning after starting two different tasks. The name and material scope let them choose the right one without opening every item.

Agree whether the package includes the selection at the time of the request or the current contents of the list. In the meantime, a customer may remove a photograph or add a drawing. Show the scope actually being prepared in the task view, and any route to create another package. Otherwise the changed list and earlier task may look like two views of the same state even though their contents differ.

Distinguish waiting to start from execution. If the task is queued, do not show that the archive is already being created. Conversely, a temporary lack of updates does not prove it has stopped. Show the state confirmed by the service and let people check again when updates are absent.

Also identify outcomes other than complete success: cancellation on request, an error and a ready result with missing material. Each calls for a different decision. One red “Failed” message does not explain whether the user should select different files, try later or collect part of the package.

For a partial result, show available and omitted items along with a reason requiring action. “Two drawings are missing” should lead people to identify them. Establish whether the incomplete package can be collected and what retry means: only missing files or a new preparation of the whole package. Button labels should preserve that distinction. Otherwise someone may retry and then be unable to tell which of two results to pass on.

Preparing the archive and downloading it to a device are two stages. “Ready to download” confirms the first. Do not say “File saved” when the person has only seen a button. A similar distinction between acceptance and outcome appears in the page after submitting a form (in Polish). For a long task it continues throughout the journey to the result.

A number should describe something counted

Carbon's progress bar guidance distinguishes progress calculable against a goal from an indeterminate indicator used when progress or completion time is unknown. The latter signals ongoing processing without giving a percentage. This distinction helps match the presentation to available information.

Before drawing a bar, establish the denominator. Prepared files, transferred bytes and completed stages do not necessarily describe the same share of the whole job. Nine small photographs and one large model may be nine out of ten files, but not nine tenths of the time. Name what you are counting.

“Prepared 9 of 10 files” gives the user specific information. Do not automatically add “A few seconds remaining”. A time estimate needs its own basis and can change. Without a reliable forecast, it is better to identify the current stage and how to return than maintain a seemingly precise clock.

When there are several stages, you can show which are complete, which is underway and what follows. Do not divide a bar into equal parts merely because there are three labels. Preparing material may take much longer than saving a link to a finished archive. Visual proportions should not pretend to measure time.

Pair a moving indicator with the name of the action. “Preparing your selected drawings and photographs” says more than a spinner alone. When the stage changes, show the new information where the person expects to find it. Do not make them follow several separate animations to understand the state of one package. If a later step needs a human decision, name it and show the available action. “Choose the missing variant” describes a different situation from “Preparation in progress”. An indicator should not imply the system is working on its own when the process is waiting for the user to supply information.

We discuss signals for short changes in website microinteractions (in Polish). Here there is also time to leave the screen. A user should not need to watch an animation for minutes just to avoid missing a one-second completion confirmation.

The message must also be available without watching the screen. WAI's explanation of status messages describes making them available to assistive technologies without moving focus, the current place of keyboard interaction, to the message. It also notes the risk of excessive announcements. A state change should inform rather than drown out the task being performed.

Aeneia conceptual photography

Decide in the design which moments need an announcement and what information makes them understandable. Hearing “nine” alone may not explain that nine files have been prepared. Accept the messages together with their context and frequency. Test with appropriate tools instead of inferring the result from how the bar looks.

Leaving the view and cancelling are separate actions

Before leaving the page, people should know what will happen to the task. If it continues independently of the open tab, indicate where to return. If closing the page actually interrupts work in the solution being used, explain the effect before exit. Do not try to settle this through button wording alone.

“Close” does not say whether it closes the progress window or stops preparation. If both actions are available, name them by their effect, for example “Return to materials” and “Cancel package preparation”. People should be able to leave the view without accidentally requesting a different operation.

For cancellation, establish whether the system immediately confirms that work has stopped or first confirms receipt of the request. If the task is still completing its current step, the status should preserve that distinction. An immediate “Cancelled” is misleading when the process might still produce a result. The design team needs to agree on behaviour with the people responsible for execution.

Consider the moment when the result has already been created. A cancellation request can arrive after completion. The screen should show the confirmed state and available actions rather than treating every intention as fulfilled. A ready file may be deleted or retained according to an agreed rule; that is a different action from stopping computation.

Returning after a break is also explored in a form completed over several sessions with saved work (in Polish). For a package, however, you are not merely restoring field contents. You are locating a task and its current result. Material selected and saved in a form does not prove preparation has finished.

When people upload their own files, also maintain the boundary between transfer and subsequent processing. Form attachments (in Polish) need clear progress and error handling. “Uploaded” should not simultaneously promise that all work on the result is complete. If there are two stages, show both.

Aeneia Design Let us design the long-running task from confirmed acceptance to collecting the result, with a clear way to leave and return. We will agree the visible states and action labels with what the service's back end can actually support. Make waiting and returning to a task clearer

On return, show the task rather than a new beginning

In Barwa, the person returns to the list of prepared packages. Each shows its name, request time and current status. They select the package for the right set of materials. If the design includes a link in a message, check that route separately: the recipient may open it on another device or after the session expires.

After sign-in, preserve a recognisable return destination. Do not automatically send someone to an empty file selection if they came to collect an existing result. If the system requires sign-in again, show the correct task and its state afterwards. Check the route from opening the message to the result view.

If the status cannot be retrieved, identify it as a reading problem. Do not immediately present it as failure of the whole task. The result may have been created even though the screen could not confirm it. A retry button should not silently start a new package when the person only wanted to refresh information about the previous one.

Also retain the time of the last confirmation if the screen continues to show the previous state. “Preparation in progress” from several minutes ago is not a current reading after a connection loss. Show the last known state with its confirmation time and a way to check again. Do not reset the bar to zero merely because the interface stopped receiving updates. Such a jump would suggest a fresh start that the system has not confirmed.

For many files, maintain their connection to the task. Linking batch results to records (in Polish) addresses this in an AI process. In the interface, the user needs a simple confirmation that they are downloading material from the selected request, not the last file generated for the whole account.

If the package expires, show that condition with the result and on the return path. After expiry, explain what is possible: prepare it again from current materials or use another available route. A new package may contain different file versions. Do not present it as recovery of an identical archive without checking its contents.

Next to a ready button, give the file name, format and size if they help someone decide whether to download. Also state the package scope and preparation time. Two similarly named lists from different days should not look identical. Once saved to a device, the file itself should remain recognisable without reopening the dashboard.

Before handing over the design, walk through several real paths in a controlled version of the service: acceptance, a long wait, leaving, returning and inability to access the status. Also check cancellation before completion and a request arriving after the result is created. This is a proposed test scope, not a claim that the tests were performed for this article.

In one trial, open the same task in two tabs. Request cancellation in the first; refresh the state in the second and check the available download button. The aim is consistency between views of one task, not creation of two independent requests. Also record what happens when the preparation button is clicked again. Users should recognise whether they are returning to an existing package or deliberately requesting another.

In the Aeneia Design offer, the waiting screen is part of the whole user journey. A prepared package should be possible to find and collect without guessing what a spinner means. Then people can attend to something else instead of personally guarding the final three percent.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear