You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After deploying my workflow and verifying that all secrets were valid, I tried to access the CF Pages site but got a 500 error instead. I looked at the CF Pages logs and saw that there was a D1 error. I checked D1 and found that no tables had been created. I ran the init.sql statement manually and that fixed the problem. I'm not sure if this is a bug or if I missed something.
Deploy the workflow and make sure all secrets are valid.
Try to access the CF Pages site.
See the 500 error and check the CF Pages logs.
Find the D1 error in the logs and check D1 for missing tables.
Run the init.sql statement manually.
Verify that the CF Pages site is accessible after running the init.sql statement.
Expected Behavior
The CF Pages site should be accessible without any issues after a successful deployment.
Actual Behavior
The CF Pages site returns a 500 error and the CF Pages logs show a D1 error due to missing tables.
Possible Solution/Workaround
Manually running the init.sql statement in the CF D1 console resolved the problem. It's possible that the statement wasn't executed during the deployment process, which caused the missing tables and D1 error.
The text was updated successfully, but these errors were encountered:
Had a chance to look at the workflow run now and I see the issue in this job:
✘ [ERROR] A request to the Cloudflare API (/accounts/***/d1/database/***/query) failed.
Internal error [code: 7501]
If you think this is a bug, please open an issue at: https://github.com/cloudflare/workers-sdk/issues/new/choose
Issue Summary
After deploying my workflow and verifying that all secrets were valid, I tried to access the CF Pages site but got a 500 error instead. I looked at the CF Pages logs and saw that there was a D1 error. I checked D1 and found that no tables had been created. I ran the init.sql statement manually and that fixed the problem. I'm not sure if this is a bug or if I missed something.
Steps to Reproduce
Expected Behavior
The CF Pages site should be accessible without any issues after a successful deployment.
Actual Behavior
The CF Pages site returns a 500 error and the CF Pages logs show a D1 error due to missing tables.
Possible Solution/Workaround
Manually running the init.sql statement in the CF D1 console resolved the problem. It's possible that the statement wasn't executed during the deployment process, which caused the missing tables and D1 error.
The text was updated successfully, but these errors were encountered: