Announcement: All noncommercial projects registered to use Earth Engine before April 15, 2025 must verify noncommercial eligibility to maintain access. If you have not verified by September 26, 2025, your access may be on hold.
WaitOperationRequest
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
The WaitOperation request message is used to wait on the completion of a specified operation resource.
The request message contains two fields: name which is the operation resource name, and timeout which is the maximum duration to wait before timing out.
The timeout field uses the Duration format and can be left blank to use the default protocol timeout.
The maximum duration to wait before timing out. If left blank, the wait will be at most the time permitted by the underlying HTTP/RPC protocol. If RPC context deadline is also specified, the shorter one will be used.
A duration in seconds with up to nine fractional digits, ending with 's'. Example: "3.5s".
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-27 UTC."],[],["The core content details the structure of a request message for the `Operations.WaitOperation`. It defines two key fields: `name`, a string specifying the operation resource's name to wait on, and `timeout`, a duration string dictating the maximum wait time. If `timeout` is not set, the wait time is limited by the HTTP/RPC protocol, or the RPC context deadline, whichever is shorter.\n"]]