Catalogue setup did not finish

The full sentence names the path, for example: "Cloud could not attach the storage this application keeps its data in: /home/node/.n8n. Attach it from the service's storage before deploying, or the application loses everything it stores each time its container is replaced."

The volume the application keeps its state in was not attached when the service was created. The application still runs, but without that volume everything it saves is lost each time its container is replaced.

Press Try again first: it asks for the same attachment again. If the sentence stays, open the service's Storage tab, press Attach volume, and give the path from the sentence as Mount path. An attachment applies at the next deploy, so press Deploy afterwards. See Volumes.

This concerns OpenClaw, the one application with first files. Cloud could not write them into its running container, or could not restart it afterwards. The files are written from the service's own variables, so it also happens when a variable they need has been removed or emptied on the Environment tab, such as OPENCLAW_GATEWAY_PASSWORD.

Check that the variables the application was created with are still set on its Environment tab, then press Try again. If the sentence stays, contact support with the project and service names.

The deployment finished, but the application's container was not running when Cloud came to write its files.

Press Start, or Deploy if the service reads Error, wait for Running, then press Try again. If it will not stay running, see The service keeps restarting.