We are still unable to understand what the fix for the "too many attempts" issue is
Status: Open · Asked by AnnaLauraHr on · 0 views
Hello again Pabbly team
We are still unable to understand what the fix for the "too many attempts" issue is. This is causing our content not to be sent to our other platform.
Can you please take a look at my video? I'll appreciate it if you can help us fix this issue as soon as possible.Also, on this video I mention another type of error we have contacted you about earlier "featured image must be a valid URL". Our image URLs have not changed nor have we changed our process for this either. Can you please help us fix these 2 items?Thanks in advance! This is urgent.
Hi @AnnaLauraHr,
https://connect.pabbly.com/workflow/mapping/IjU3NjUwNTY1MDYzNTA0MzU1MjZmNTUzNDUxMzYi_pc
If you're encountering a "too many attempts" error while trying to execute an endpoint, it typically indicates that you've exceeded the rate limit set by the server or API you're interacting with. This limit varies for different applications and is set by the application itself. Since we don't have a direct integration with the application whose endpoint you are trying to execute, we don't have any information on it.
Check the API documentation of the endpoint you are trying to execute to understand its rate limit. This will usually tell you how many requests you can make in a given time period.
If you believe you're not exceeding the rate limits or need a higher limit, contact the application's support team for assistance.
================================================================================
https://forum.pabbly.com/threads/issues-with-the-featured-images.22750/post-109452
Regarding the "The feature image field must be a valid URL" error you are encountering, as mentioned previously, it is a result of the image URL you are trying to upload behaving differently on different occasions. Sometimes it directs to a website, and other times it acts as a direct URL. This inconsistency is causing some images to be uploaded without any issues while others encounter an error.
You can see this inconsistency in the image URL's behavior in the video shared below:
https://drive.google.com/file/d/1TxbfiyQO5NN_j89XDeirb7U4E6uJOvoV/view
The way an image is processed is handled at your server's end; we cannot do anything about it at our end.