
TypeScript
import { Client, Databases, Query } from 'node-appwrite';
export default async ({ req, res, log, error }) => {
const client = new Client()
.setEndpoint(process.env.VITE_APPWRITE_ENDPOINT)
.setProject(process.env.VITE_APPWRITE_PROJECT)
.setKey(process.env.VITE_APPWRITE_API_KEY);
const databases = new Databases(client);
try {
console.log("UpdateShiftsOrders");
const {documents,total} = await databases.listDocuments(
process.env.VITE_APPWRITE_DATABASE_ID_EKHLAS,
process.env.VITE_APPWRITE_COLLECTION_ORDERS_ID,
[
Query.equal('status', 'DONE'),
]
);
console.log("Documents",orders);
documents.forEach(order => {
console.log("Order",order);
});
return res.send("Done");
} catch (e) {
console.log("Error",e);
return res.send(e);
}
};
this is my cloud function code but when i loop it this happens
TypeScript
An internal curl error has occurred within the executor! Error Msg: Http invalid protocol\nError Code: 500
and what causes this?
TL;DR
When developers use a loop in their cloud function, they encounter an error: "An internal curl error has occurred within the executor! Error Msg: Http invalid protocol\nError Code: 500." This error is caused by an issue in the implementation of the loop within the cloud function. The specific cause should be reviewed and corrected in the loop logic to resolve the error.Recommended threads
- 500 Server Error after migrating to 1.8....
Upgraded as per docs and ran migration. Everything went smoothly. I am able to log into the appwrite console however cant access any service i.e., auth, databas...
- Console not showing Site screenshot
Image link broken for self-hosted 1.8.0 (updated from 1.7.4), was working fine in older Console version (6.0.43, updated to 7.4.10).
- Storage usage keeps going up
I have a self-hosted instance running in production for over a year now. The deployment has seen multiple updates and migrations of Appwrite versions. What I ha...
