Jorge Caballero

> @DataDrivenMD You shouldn't use the default "Cloudflare Workers" API token template. There's a deploy button in the README that has a link to create an API token with the...

@koehn: I ran into this issue earlier > [29](https://github.com/koehn/wildebeest/actions/runs/4136772123/jobs/7151559387#step:19:30) > In order to use Durable Objects, you must agree to pricing at https://dash.cloudflare.com/***/workers/overview?enable-durable-objects [code: 10084] The fix is to replace...

@xmflsct I can confirm that I am on the new managed rule interface

> @DataDrivenMD sorry deleted my previous message. Digged a bit more, you should have deployed managed rules already in that target zone. If that is the case, for now a...

> OK, just made sure my repo was sync’ed, enabled DO, Enabled Access, and now this error in the “Download Terraform State” task: > > ``` > ✘ [ERROR] Failed...

@yawnbox > So... I did this `Visit the Access dashboard at https://dash.cloudflare.com/ and click the 'Enable Access' button.` and there is no such button. It's been re-branded as "Zero Trust"...

> I encountered simillar situation. I tried deployment but GitHub Action failed due to payment approval. Then I approved payment and re-run action to fail. > > Situation is getting...

> That is likely you have deployed rules in the past through the dashboard UI, hence an entrypoint ruleset had been automatically created by the UI behind the scene. Tested...

> I walked through the pointless setting up of a free Zero Trust thing in which it charged my credit card $0. Re-ran the deploy, new error. That means you...

After further testing, I think this PR merits a clarification: this isn't meant to fix **all** 3rd-party app incompatibilities, just those that invoke `GET /api/v1/apps/verify_credentials` during their onboarding process. I'm...