[SOLVED] Rate limits applied to Function | Appwrite | Page 1

coarse sequoia Jan 11, 2025, 12:30 PM

#

Hello, I'm curios what statement is correct and is it a bug or not. Here is the documentation screenshot and my function execution logs.

"Rate limits do not apply when accessing Appwrite with a Server SDK authenticated using an API key." - Docs
"Error creating pending account: Rate limit for the current endpoint has been exceeded. Please try again after some time." - Cloud function log

viral siren Jan 12, 2025, 4:44 AM

#

Error creating pending account doesn't seem to be an appwrite exception message.
can you show the relevant part of the code where you get this error?

coarse sequoia Jan 12, 2025, 1:37 PM

#

async function processPendingAccountsBatch(databases, databaseId, pendingAccountsCollectionId, leads, userId, customer) {
  // Step 4: Create PendingAccount docs
  const pendingAccounts = await Promise.all(leads.map(async (leadDoc) => {
    try {
      const pendingAccount = await databases.createDocument(databaseId, pendingAccountsCollectionId, 'unique()', { status: 'pending', userId });
      console.error("Created pending account:", pendingAccount);
      return pendingAccount;
    } catch (error) {
      console.error("Error creating pending account:", error.message);
      return null;
    }
  }));

#

Hello Darshan Pandya, as you can see the error is raised by createDocument with the rate limit error

#

which should be impossible by design and documents provided

viral siren Jan 12, 2025, 2:12 PM

#

is the Client using API Key or a Session? Can you share the code related to client? using API KEY should not throw a rate limit.

coarse sequoia Jan 12, 2025, 2:13 PM

#

It's about API key, as it is a appwrite function

#

it's not from client

#

#

@viral siren Error creating pending account: Rate limit for the current endpoint has been exceeded. Please try again after some time.

#

"Rate limit for the current endpoint has been exceeded. Please try again after some time." - is this not a rate limit error thrown by appwrite?

viral siren Jan 12, 2025, 2:16 PM

#

dynamic api key or a standard api key?
also share how you are creating the Client

coarse sequoia Jan 12, 2025, 2:17 PM

#

standard api key

import { Client, Databases, Storage, ID, InputFile, Query } from 'node-appwrite';

// 3. Init Appwrite SDK
    const client = new Client()
      .setEndpoint('https://cloud.appwrite.io/v1')  // Provided by Appwrite
      .setProject('') // Provided by Appwrite
      .setKey(process.env.APPWRITE_API_KEY);               // Secret API key from Function's ENV
    const databases = new Databases(client);

loud crest Jan 12, 2025, 3:55 PM

#

coarse sequoia standard api key ``` import { Client, Databases, Storage, ID, InputFile, Query }...

Do you have set scopes for databases?

coarse sequoia Jan 12, 2025, 5:42 PM

#

nope

loud crest Jan 12, 2025, 6:00 PM

#

coarse sequoia nope

Then you're interacting like if you did not have an API key. Consequently you're rate limited. You should have set the scopes for databases in the API Key settings

#

Or use dynamic API Keys

coarse sequoia Jan 12, 2025, 6:09 PM

#

[SOLVED] Rate limits applied to Function

loud crest Jan 12, 2025, 6:34 PM

#

@coarse sequoia So that worked, right? Make sure to not expose the API key accidentally as it overrides all permissions 😅

#[SOLVED] Rate limits applied to Function