-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Error in documentation for receive_messages #21378
Copy link
Copy link
Closed
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.DocsService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.StorageStorage Service (Queues, Blobs, Files)Storage Service (Queues, Blobs, Files)bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK team
Description
This is related to bug 19373: #19373
The documentation on docs.microsoft.com says that the minimum value for visibility_timeout is 0, when in fact it is 1. Also, it does not mention that the maximum for messages_per_page is 32. The visibility timeout limit is also incorrectly stated here.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: ca4d7b94-75d7-236c-517a-9ce46628a292
- Version Independent ID: 6a535359-e284-bc61-5be4-ae2bbd968d87
- Content: azure.storage.queue.QueueClient class
- Content Source: docs-ref-autogen/azure-storage-queue/azure.storage.queue.QueueClient.yml
- GitHub Login: @lmazuel
- Microsoft Alias: lmazuel
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.DocsService AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.StorageStorage Service (Queues, Blobs, Files)Storage Service (Queues, Blobs, Files)bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK team