Cloudflare Developers•13mo ago

Deployment Error: workers.api.error.placement_and_triggers_configured (100150)

Hi all! I'm suddenly getting the following error when trying to deploy an worker, as the error might indicate, we do have placements set to smart and we have a queue consumer / producer set in the same worker. I feel like this didn't happen before and wonder what changed, and if it's not possible to have smart placements enabled with queue consumers / producers?

29 Replies

ItsWendell•13mo ago

I feel like this did work before, turning off smart placement with [placement] mode = "off" gives me workers.api.error.unknown [code: 10013]. Turning off smart placement in the dashboard also gives me An unknown error occured. (Code: 10013) We don't have any cron bindings in wrangler.toml, we did export a scheduled function (for once we enabled a cron job), but even after commenting this out the same issue happens 7f80802cc22f5b5cc65331d4e2523f79 - api-service-prod

Vero•13mo ago

raising

ItsWendell•13mo ago

Maybe relevant to know, probably not, saw the incident in IAD this morning, our worker might have been smart placed there since we have one of our data services running there I believe

Vero•13mo ago

Smart placement doesn’t work with cron triggers. They'll check the unknown error in 1h or so

ItsWendell•13mo ago

@veerooo that's good to know, but we currently don't have any cron triggers, only queues / KV. We did have a scheduled function exported (for once we start using cron triggers), but even after commenting it out and re-deploying same issue occurs.

ItsWendell•13mo ago

@veerooo let me know if anything else is needed, would love to deploy again as soon as possible!

Vero•13mo ago

they say they aren't sure commenting out scheduled cron triggers works as expected. They've had problems with this in the past, and ended up having to create an empty array for the cron trigger in wrangler.toml to make it go away not sure if that happens with scheduled functions

ItsWendell•13mo ago

Same result with the scheduled function removed, and with

[placement]
mode = "smart"

[triggers]
crons = []

[placement]
mode = "smart"

[triggers]
crons = []

In my wrangler.toml

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Alright, keep me posted!

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Correct,

mode = "off"

[triggers]
crons = []

mode = "off"

[triggers]
crons = []

is giving me workers.api.error.unknown [code: 10013]

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

[placement]
mode = "smart"

[triggers]
crons = []

[placement]
mode = "smart"

[triggers]
crons = []

is giving me workers.api.error.placement_and_triggers_configured [code: 100150]

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Yeah @mhart I can sent you full configuration of my toml file if needed

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

@mhart as long as I can deploy again that would be great!

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

@mhart no results:

curl --request PUT \
  --url https://api.cloudflare.com/client/v4/accounts/7f80802cc22f5b5cc65331d4e2523f79/workers/scripts/api-service-prod/schedules \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer XXX' \
  --data '[]'

{
  "result": {
    "schedules": []
  },
  "success": true,
  "errors": [],
  "messages": []
}

curl --request PUT \
  --url https://api.cloudflare.com/client/v4/accounts/7f80802cc22f5b5cc65331d4e2523f79/workers/scripts/api-service-prod/schedules \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer XXX' \
  --data '[]'

{
  "result": {
    "schedules": []
  },
  "success": true,
  "errors": [],
  "messages": []
}

workers.api.error.placement_and_triggers_configured [code: 100150]

workers.api.error.placement_and_triggers_configured [code: 100150]

Also get request is return this:

{
  "result": {
    "schedules": []
  },
  "success": true,
  "errors": [],
  "messages": []
}

{
  "result": {
    "schedules": []
  },
  "success": true,
  "errors": [],
  "messages": []
}

@mhart Can you confirm whether this is still being looked into?

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Yes completely removed

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Appreciate the support! So it was just having a scheduled handler in my worker that caused it to register as a cron worker? I don't think we ever had it registered in wrangler.toml @mhart any updates? Seems like we're still receiving the same error:

  workers.api.error.placement_and_triggers_configured [code: 100150]

  workers.api.error.placement_and_triggers_configured [code: 100150]

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Seems like I can deploy now with smart placements on*! Thanks for fixing this! Would love to hear about the recommendations around crons / smart placements for when we actually implement crons, then we might do it in another worker!

Unknown User•13mo ago

Message Not Public

ItsWendell•13mo ago

Yeah makes sense, people might have a single worker handling different things though: queues, api routes, jobs

Unknown User•13mo ago

Message Not Public

Gaming

Programming

Deployment Error: workers.api.error.placement_and_triggers_configured (100150)