You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, we register a worker to receive work from that queue, with a label of `Some-Skill` equal to 11.
158
158
```python
159
-
from azure.communication.jobrouter import (
159
+
from azure.communication.jobrouter.modelsimport (
160
160
RouterWorker,
161
161
ChannelConfiguration
162
162
)
@@ -209,7 +209,7 @@ for event in events:
209
209
210
210
However, we could also wait a few seconds and then query the worker directly against the JobRouter API to see if an offer was issued to it.
211
211
```python
212
-
from azure.communication.jobrouter import (
212
+
from azure.communication.jobrouter.modelsimport (
213
213
RouterWorker,
214
214
)
215
215
@@ -221,7 +221,7 @@ for offer in router_worker.offers:
221
221
### Accept an offer
222
222
Once a worker receives an offer, it can take two possible actions: accept or decline. We are going to accept the offer.
223
223
```python
224
-
from azure.communication.jobrouter import (
224
+
from azure.communication.jobrouter.modelsimport (
225
225
RouterJobOffer,
226
226
AcceptJobOfferResult,
227
227
RouterJobStatus
@@ -262,7 +262,7 @@ print(f"Job has been successfully completed.")
262
262
### Closing a job
263
263
After a job has been completed, the worker can perform wrap up actions to the job before closing the job and finally releasing its capacity to accept more incoming jobs
0 commit comments