When deploying, what does the error `placement_and_triggers_configured` mean?
I am using Wrangler 2.2 (cannot upgrade to 3 for technical limitations), and when I run
wrangler publish, I am met with the following error: workers.api.error.placement_and_triggers_configured [code: 100150]. Using the --dry-run flag, I do not receive an error.5 Replies
I believe it's just saying that you cannot have smart placement with cron triggers at the moment. If that's what you have, that's why. Have to disable smart placement
Oh interesting. I don't remember what smart placement is, but I added it based on a recommendation. Is there a reason one can't have both?
My worker uses both a
fetch and scheduled handler, so I'd like the fetch to be smart, even though the scheduled handler runs on cron.Smart placement is helpful if you are doing a bunch of fetches in each request to a remote origin. Instead of the request being like Visitor -> local Colo executing Worker < ---- Long request to origin --> origin, the Worker runs near the origin you are fetching (Visitor -> Remote colo executing Worker <- low latency to origin/fetch target -> orrigin
https://blog.cloudflare.com/announcing-workers-smart-placement/
I'm not aware of any real reason other then it just breaks crons from running, so they've disabled it for now
Looks like for now they've just said that cron jobs are not a good use for smart placement, and for now they recommend seperating out the cron into a seperate worker if smart placement is needed: https://discord.com/channels/595317990191398933/1111627637912244254/1111765153445314582
Thank you so much. I did a search for the error string but it somehow didn't come up in my results. 🙂
No worries, "triggers" is pretty vague and could be a lot of things , not the best error code