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
It seems like unsetting a worker's team is presently impossible on the v2 API:
tinybots.net/artbot sends a payload with "team": null which fails type validation for the parameter.
artbot.site (v2) sends an empty string as suggested in the endpoint doc, but the server responds with HTTP 500 (briefly alluded to in feat: implement worker management artbot#56)
Both ArtBot deployments send the team ID with each Update Single Worker request - so as a side effect, both appear to be unable to update the name/info fields for workers unless a team is selected.
I have confirmed the null/"" responses and inability to update info/name when sending either empty team value in the payload via Postman, as well.
It seems like unsetting a worker's team is presently impossible on the v2 API:
tinybots.net/artbotsends a payload with"team": nullwhich fails type validation for the parameter.artbot.site(v2) sends an empty string as suggested in the endpoint doc, but the server responds with HTTP 500 (briefly alluded to in feat: implement worker management artbot#56)Both ArtBot deployments send the team ID with each Update Single Worker request - so as a side effect, both appear to be unable to update the
name/infofields for workers unless a team is selected.I have confirmed the
null/""responses and inability to updateinfo/namewhen sending either emptyteamvalue in the payload via Postman, as well.