
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
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Looking for Partner
I'm looking for partner for long-term collaborating. Of course, I'll pay for you. If you are interested, Please DM me.
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
