[Question] Implementing Long-Running Operations with SyncPoller

[danielszaniszlo]

[Question] Implementing Long-Running Operations with SyncPoller

[alzimmermsft]

Hi @danielszaniszlo, this exception is thrown when all polling strategies return false when calling canPoll. In the generated code only the custom strategy is added and that uses the default canPoll for the super type OperationResourcePollingStrategy which simply checks:

• Does the response have the operation location header?
• Does the polling endpoint and / or the operation location header create a valid URL?

If one, or both, of those fail this exception will be thrown. This is a case where some debugging is needed on the initial response to make sure the above holds true.

[danielszaniszlo]

HI @alzimmermsft, Thanks for the quick reply. The polling endpoint url is valid and the initial response is successful too, but it doesn't have the operation-location Header.

What URL should be in the operation-location header?

In our case the request PUT https://endpoint/jobs/{name} is the original request which creates a job and with
GET https://endpoint/jobs/{name} you can query the created job status

[alzimmermsft]

Pulling in @srnagar and @weidongxu-microsoft as this differs from the expected pattern of OperationResourcePollingStrategy polling. Do we have any design recommendations for the pattern above?