# Endless startup, build or no logs

## Endless Run

Accompanied by the status “build completed successfully, launch in progress.”

- If the "Startup in progress" status is observed for more than 5 minutes, this indicates an error in the configuration file or its absence.

- Or your application needs to use a higher tariff (requires more resources to run). We recommend choosing one of the older tariffs during the first build and then changing it. After launch, you can change the tariff in Settings to the one at which the application works and which suits you for the price.

## Endless build

Building projects in Amverum Cloud takes longer than on a local machine.
Average assembly time is 5-20 minutes. In rare cases, assembly can take up to 30-60 minutes.

- If your project is in the “build” status for more than an hour and there are no logs, it means the build ended with an error and
It is worth making sure that the configuration file is correct.
- Or your application needs to use a higher tariff (requires more resources to run). We recommend choosing one of the older tariffs during the first build and then changing it. After launch, you can change the tariff in Settings to the one at which the application works and which suits you for the price.


## Project stuck during build/run
However, it is not possible to control it in the interface (the rebuild/restart buttons are inactive)

Symptoms of this problem are the build/launch status for more than 30 minutes and inactive buttons in the interface. 
This is either because your project is complex and requires a long build time.

1. Try to wait a little (20-30 minutes). Some projects take a long time to assemble/launch and additional actions 
will simply cause the process to start all over again.
2. If nothing happens, try starting the build process again using the "Build" button on the "Configuration" tab. You can first remove files from the artifacts folder.
3. If you use a Dockerfile without `amverum.yaml`, then instead of the previous action you need to make formal changes to the repository and push them into Amverum.
4. Try increasing your tariff. Your application may not have enough resource to run.
5. If nothing helps, recreate the project (preferably with a new name) and write to us in support support@amverum.ru. We'll figure it out together.

## No logs

An architectural feature of our system is that logs in the interface are displayed with a delay. Delay may 
be about 2-5 minutes - this is a normal situation.

At the bottom of the screen there is a button (clock) to manually load the history. After clicking the button, the logs will be downloaded in approximately 1-3 minutes.

![quick-start2](../../img/load_logs.png)


If there are no “Build” logs for more than 20 minutes, then you have one of the following problems

- logs are written in print (when using Python). To display logs from print, you need to set the project environment variable PYTHONUNBUFFERED to 1
- push did not reach master
- no configuration file
- the assembly froze with an error
- in some cases (they did not arrive the first time), clicking the “rebuild” or “restart” button in the interface and pressing the log download button again can help.
- the selected tariff is not enough for assembly. We recommend starting with one of the older tariffs and then changing it.

If there are no "Application" logs, but the build was completed "successfully", read [this section](502-503-error.md)

```{eval-rst}
.. admonition:: Clue
   :class: hint

   If you can’t figure it out, write to support support@amverum.com. Please immediately indicate your user and project name. We will try to help. 
```