"internal error" error while using service binding.
Hi,
I have two workers. One worker (Worker A) is trying to make an API call to another worker (Worker B). I have enabled the service binding where I have bound Worker A with Worker B, and when I'm trying to call the API, I'm getting this error log in Worker B:
internal error; reference = 01d9n3paq7mnnnamd35rml8p. This is how I'm calling the API: await env.data_injection_worker.fetch(aktoReq);.16 Replies
Hey, are you seeing this consistently? Can you also link your account please
?link
Please use the /link command to authenticate with your Cloudflare account and link it to your Discord user. This helps Cloudflare employees access your details more quickly and provide support. It also makes future support requests easier, since your account will already be linked.
done
yup!
its consistent
interesting, can you provide some more ref ids? Sadly that one wasn't captured
sure
and when did this start? was it always happening since you set this up or it broke at some point?
internal error; reference = 03t1v147q4l2st6bqkke3cp4
It was working about 10 days ago, but now, when I'm trying the service binding thing with a new worker, it's not working.
without service binding i'm able to call the API
let me know if you need more info
I need to fix this issue ASAP because in few hours I have a client call.
:NotLikeThis:
Ok so I can see the internal error - it looks like MyContainer is being called as a DO but it doesn't exist as a DO (which is a strange state)
did you happen to do something like rename or delete this but still have a script referencing it as a binding?
Nope
It's a new container
does the ingest worker still use MyContainer as the container/entrypoint name?
yes i guess
yeah i can see it being used the same.. hmm, not sure how you got into this state
What's the issue?
I mean, 10 days ago it was working with the same configuration.
Now I have deleted that container and those workers, created new ones, and now it's not working.
this is the issue but why, i do not know
It seems you re-creating these got it into a weird state for some reason. I'd love to know how haha
I have no idea about this :)
So, what should I do? Do you have any ideas?
š
any help here? š
I tried deleting old containers, workers, and durable objects and tried redeploying everything, but it's still giving me an internal error.
I really need to resolve this today.