• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Could Not Send: limit on number of agreements reached

New Here ,
Dec 20, 2023 Dec 20, 2023

Copy link to clipboard

Copied

As in the title, I have a user receieving an error message when trying to send an e-signature request. What I've read indicates that it's an issue with transaction throttling, however only about 15 requests were made in the morning before getting this error, and less than 200 within the last 24 hours. This is by no means uncommon or heavy usage, and we've never recieved this message before. The user in question is licensed for Adobe Pro, and while the article I read was frustratingly vague on exactly how much it would take to trigger this error, that seems extremely low. Is there something else that could potentially be giving this message? Or some way to find more details about what caused it, in case it's being caused by duplicate requests or something of that nature?

 

Stanley34383233z4al_0-1703101914319.png

 

TOPICS
Adobe Sign forms , Send documents

Views

601

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 21, 2023 Dec 21, 2023

Copy link to clipboard

Copied

Hi Stanley34383233z4al,

 

Thank you for reaching out.

 

As you get the error, it is most likely the transaction throttling. The rate of resource consumption by the same consumer (eg: the same user ID, IP address, agreement IDs, etc.) is limited (throttled) by the minute, hour, and day.

In the error message, it is mentioned to try again after 3 hours. Please try after 3 hours and see if you still get the error.

 

Thanks,

Meenakshi

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 29, 2023 Dec 29, 2023

Copy link to clipboard

Copied

LATEST

We did not receive the error again after three hours, and haven't since. That doesn't really help us going forward in the future, but I guess "Tell the user to wait it out" will have to do.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines