Progress & Tasks: Monitor Your Transfers

The Progress page lists your tasks. It shows how far each transfer has got, and it is where you pause, resume or cancel one.

When you start a workflow, Blober creates a task. A task is a single run of a workflow, and it tracks:

• which files need to be transferred
• current progress, in files and bytes
• the status of each file
• logs and error messages

You can run the same workflow as often as you like. Each run creates a new task.

1. Go to the Workflows page.
2. Find the workflow you want to run.
3. Click Run.
4. Blober creates a new task, and it starts running.

1. Blober finds the files that match your source selection and your filters.
2. It transfers them, and the progress updates as each file finishes.
3. The task status changes to completed or failed.

1. Find the running task.
2. Click Pause.
3. The task stops, and its status changes to Paused. Files that finished stay done.

Pausing frees up bandwidth for other work, or lets you look into a problem without losing progress. You can resume whenever it suits you.

1. Find the paused task.
2. Click Resume.
3. The task continues with the files that are not done, and its status changes to Running. A file that was stopped partway starts again.

1. Find the task. It can be running or paused.
2. Click Cancel.
3. The task moves to Stopping, and after cleanup its status changes to Cancelled.

Files that were already transferred stay at the destination, and the file in progress may be left partly transferred. Source files are unchanged, unless the action is Move and some files had already finished moving.

Each task shows its progress as it runs:

Blober does not count the source before it starts. It finds the files while it transfers them, so the total is known only when the task completes. Until then, the line shows only what is done. This is also true for a task that is paused, cancelled or failed. Until the task completes, the bars compare the done files with the files found so far, not with the full source.

For large files, you may also see the file currently being transferred, how many of its bytes have been sent, and the transfer speed.

Each task keeps a log of what it did.

Within a task, each file has its own status:

Blober retries failed operations on its own when the cause is a network timeout, rate limiting or a temporary provider error.

If some files fail, the ones that transferred stay at the destination and the failed ones are logged with their error messages. You can start a new task to retry them.

Completed and cancelled tasks stay in the list, so you can review what was transferred and check for errors when troubleshooting.

1. Use a wired connection. It is more stable than Wi-Fi.
2. Close other applications to free up bandwidth and CPU.
3. Transfer during off-peak hours, when the network is less congested.
4. For cloud providers, pick the region closest to you.

With thousands of files, progress is slow at first while Blober finds the files, and then speeds up. You can also split the transfer into smaller batches.

If a task is interrupted:

1. Don't delete the task.
2. Click Resume to continue.
3. Blober skips the files it already transferred.

• Check whether another task is running.
• Check your internet connection.
• Restart the app if needed.

• Check your internet speed.
• Check whether the provider is rate limiting you.
• Try smaller batches.

• Check the credentials in the workflow.
• Check that the source path exists.
• Check that you have write access to the destination.

• Check that the path template is correct.
• Check that filters aren't excluding the files.
• Look in subfolders, if the workflow uses a path template.