{"version":"2.1.232","anchor":"agent-lists-say-when-cloud-sessions-could-not-be-fetched","canonical_anchor":"agent-lists-say-when-cloud-sessions-could-not-be-fetched","heading":"Agent lists say when cloud sessions could not be fetched","tier":"use","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/agent-lists-say-when-cloud-sessions-could-not-be-fetched","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Agent lists say when cloud sessions could not be fetched\n\n\/list-agents now says when the cloud session list couldn't be fetched instead of looking empty.\n\n**What**\n\n`\/list-agents` and the send-message error paths now say outright when the cloud session list could not be retrieved, so a session missing from the list is not mistaken for a session that does not exist.\n\n**Details**\n\n- Separate wordings cover the listing itself, the case where cloud sessions were not searched at all, and a warning that the list may be missing a cloud session.\n\n**Evidence**\n\n`The cloud session list could not be fetched just now, so cloud sessions were not searched.`\n\n- Area: Agents\n- Names: `\/list-agents`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}