• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

"Create Multi Image Post" for Facebook Pages – Error Code 324

Hi,
I'm having trouble using the "Create Multi Image Post" action for Facebook Pages in Pabbly. Every time I try to use it with more than one image, I get the following error:


Res2 Result Uploaded Media Fbids Error Type: OAuthException
Res2 Result Uploaded Media Fbids Erro Code: 324
Res2 Result Uploaded Media Fbids Erro Error User Message: Make sure your Page post includes an image that can be used in an ad.


I've tried with different images and formats, but it always fails when uploading more than one. Strangely, if I only select a single image, the post goes through without any issues.


Does anyone know why this is happening? Is there a limitation on Facebook's side or with the Pabbly integration?


Any help or suggestions would be greatly appreciated.
 

Preeti Paryani

Well-known member
Staff member
Hello @joaquinrojas42,

Thank you for sharing the workflow.

Upon attempting to access the image URL used in the Create Multi-Page Post action, we encountered the error: "URL Signature Expired." This suggests that the issue lies with the image URL. We recommend trying a different image with a valid, active URL.

1744973360520.png


Additionally, we noticed that the trigger is still waiting for a response, which might have caused the webhook to expire. If new responses are not being captured, we suggest creating a new workflow to ensure proper trigger functionality.

1744973372056.png
 
Top