Resume unfinished cloud connections
Cloud accounts distinguish unfinished setup from an active access check. A verified observation connection counts as connected even when permission to run workloads still needs setup. Unobserved inventory shows a dash instead of zero, and failed inventory reads offer a retry without an empty results table. An empty inventory object received before the first successful sync also stays unknown.
Use Continue setup to resume the same AWS, Google Cloud or Azure account. Recovery commands have a copy
button. The CLI command nodus cloud onboarding ACCOUNT fetches setup instructions for an existing account;
it replaces the unsupported nodus get ... --subresource onboarding suggestion.
Google authorization parameters are removed from the return URL on both success and failure. When Google reports a disabled API or billing account, verification explains which setup needs attention. Retrying a failed project selection submits the preserved selection again instead of reloading the project list. A temporary failure while fetching setup instructions preserves the account so it can be resumed safely. Unfinished or revoked execution grants offer their setup instructions again when you return to the account. Revoked cloud roles ask you to restore execution access instead of requesting an API key.