sdr Comments - Answer Overflow

sdr

•Created by Sameer Ali on 3/4/2025 in #workflows

It might be naive question but i am

Ive experienced this too, where logs seem to get swallowed on an exception. Or they take 1-2 mins to show up. My only "fix" was to run them again, add more try catch inside of the step and try and log from there

3 replies

CDCloudflare Developers

•Created by sdr on 3/2/2025 in #workers-help

Fetch to Google APIs timeout in prod

Thanks for your help!

8 replies

CDCloudflare Developers

•Created by sdr on 3/2/2025 in #workers-help

Fetch to Google APIs timeout in prod

Its prob something small and dumb. If not I'll spin up a separate node app on railway or something and see if it just works there

8 replies

CDCloudflare Developers

•Created by sdr on 3/2/2025 in #workers-help

Fetch to Google APIs timeout in prod

Yeah good advice, I think I need to just pare it back a basic implementation to identify the problem. I havent had problems with fetch before to other services in other react-router apps on cloudflare

8 replies

CDCloudflare Developers

•Created by sdr on 3/2/2025 in #workers-help

Fetch to Google APIs timeout in prod

It works in local dev, and when I copy the same prod params and use them in a curl command it works so Im thinking its a runtime environment thing? But I could be dumb and just not see something obvious, but at this stage Im blind

8 replies

CDCloudflare Developers

•Created by sdr on 3/2/2025 in #workers-help

Fetch to Google APIs timeout in prod

Its part of a broader app but its a react-router app which has a loader function. I have a GoogleClient class which I init with the relevant client id, secret, and user refresh token. The fetch call which hangs looks like this

const response = await fetch('https://oauth2.googleapis.com/token', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/x-www-form-urlencoded',
  },
  body: new URLSearchParams({
    client_id: this.clientId,
    client_secret: this.clientSecret,
    refresh_token: this.integration.refreshToken!,
    grant_type: 'refresh_token',
  }),
  signal,
})

const response = await fetch('https://oauth2.googleapis.com/token', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/x-www-form-urlencoded',
  },
  body: new URLSearchParams({
    client_id: this.clientId,
    client_secret: this.clientSecret,
    refresh_token: this.integration.refreshToken!,
    grant_type: 'refresh_token',
  }),
  signal,
})

I pass in an abort controller signal which I used to kill the request after 10s

8 replies

CDCloudflare Developers

•Created by telliks on 11/20/2024 in #workflows

Sure, I can share some pieces that I

I don't think theres any extra scaffolding that it does, theres likely something very small off with your setup but I can't quite spot it

13 replies

CDCloudflare Developers

•Created by telliks on 11/20/2024 in #workflows

Sure, I can share some pieces that I

Yeah I just ran it with the cli tool and used the defaults npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter" Id say try do it from scratch in an independent worker to get it setup first and then migrate what works into your existing hono app

13 replies

CDCloudflare Developers

•Created by telliks on 11/20/2024 in #workflows

Sure, I can share some pieces that I

Maybe your workflow needs to have its run function defined? export class ProcessIncomingEmailsWorkflow extends WorkflowEntrypoint< Bindings, Params

{

async run(event: WorkflowEvent<Params>, step: WorkflowStep) { const done = await step.do('work', async () => { return true }); return done } }

13 replies

CDCloudflare Developers

•Created by telliks on 11/20/2024 in #workflows

Sure, I can share some pieces that I

Ah yeah that might be it. I might have an older config. Theres a PR around clarifying that here https://github.com/cloudflare/cloudflare-docs/pull/17770/files

13 replies

CDCloudflare Developers

•Created by telliks on 11/20/2024 in #workflows

Sure, I can share some pieces that I

You might be missing the script_name key from your wrangler.toml workflows section [[workflows]] ... script_name = "process-incoming-emails"

13 replies

CDCloudflare Developers

•Created by Seekerdasbatatas on 10/28/2024 in #workflows

You are only charged for CPU cycles **

Is it planned to show CPU time on the dashboard?

2 replies

CDCloudflare Developers

•Created by sdr on 10/27/2024 in #workflows

Also I notice that the step name listed

Yeah maybe its attempts. It would be strange to have a dynamic step name though

9 replies

Gaming

Programming