Enable workers nothing happens

Great news guys! Looking forward to test it out soon! Youre quick with the updates, I like it!

Thanks! I exported and imported and reinserted global API etc. Tried to enable workers. Nothing happens I do not see any workers script added by your plugin.

Hi @alriksson,
That is really wired. Can you show me a screenshot of the workers page in your CF dashboard? Also if there is any existing workers added by you show me the route added to them as well.

Can I share over email?

Hi @alriksson,
You can share the screenshots I’ve asked for here. Those screenshots have nothing sensitive in them.

I blurred them as they contain sensetive informaiton and anyhow not useful for your in this case.
https://prnt.sc/vlk4kv
https://prnt.sc/vlk6bp
https://prnt.sc/vlk7ut

So I have 2 routes from before and 1 old KV since i used the original html_edge_cache workers before, but stopped worked after a while and wasn’t maintained. But don’t see why any of these could cause any issue for your plugin through the API? Maybe a log from the plugin could be useful here if it’s possible to get one if the API fails from Cloudflare?

My only idea is that you try to add a route with the exact same name as I already have? And that cause issues but we have no log of information from the API that can give us better informaiton about what or why it isn’t working?

As I’ve blurred this is the routes in this example:
domain.com/*
staging.domain.com/*

But if I remember it right you did not use this route? With .*domain.com/* or absolute path with wild card in the end to catch everything after that. Maybe could cause issues anyhow? Let me know.

• This reply was modified 4 years ago by Rookie.
• This reply was modified 4 years ago by Rookie.
• This reply was modified 4 years ago by Rookie.

Hi @alriksson,
Yes we don’t use routes like that we use absolute routes like https://domain.com/* as a route. And you are saying that when you are enabling worker mode in the plugin the workers are not getting added in your Cloudflare account? Maybe domain.com/* taking precedence over our absolute route. Can you try deleting just the domain.com/* route (not your custom worker) and see what happens?

Sorry for the late reply. I will try this tomorrow, disable and enable workers to see if the route and workers script gets added.