Argument “input” has invalid value across multiple networks

  • laconicsky

    (@laconicsky)


    23 hours, 27 minutes ago

    Hello,

    I am experiencing a recurring error when attempting to send posts to Buffer (specifically targeting Facebook and LinkedIn). Whenever a post is published or updated, the status fails to send, and I receive the following error message across all connected networks:

    Argument "input" has invalid value { channelId: $channelId text: $text schedulingType: $schedulingType mode: $mode source: $source dueAt: $dueAt saveToDraft: $saveToDraft assets: $assets metadata: $metadata }.

    Here are the troubleshooting steps I have already taken to try and resolve the issue:

    • Updated the plugin to the latest version.
    • Disconnected and re-authorised the Buffer connection.
    • Confirmed that the attached featured images are in standard formats (JPEG or PNG) and meet the minimum size requirements for social sharing.

    Despite these steps, the raw log continues to show this generic GraphQL rejection. Because the error acts as a catch-all and does not specify which exact variable (such as $assets or $dueAt) is failing validation, I am struggling to pinpoint the underlying cause.

    Is there a way to enable more verbose logging to see exactly which field Buffer is rejecting? Any guidance on how to isolate and resolve this formatting conflict would be greatly appreciated.

    Thank you in advance for your help.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter laconicsky

    (@laconicsky)

    21 hours, 21 minutes ago

    The error occurs when the type of status is Link but there is nothing netted in the

    “Link

    The “primary” URL to use for the link preview / card. Additional links can be included in the status text above.”

    section. As soon as a parameter is entered here the post gets submitted to Buffer.

    however I have {url} in here but in buffer its showing the post date. Why is this and how do I fix? Thanks.

    Screenshot of dashboard (showing {url} at bottom):

    https://cln.sh/JVyXX9XJ

    Screenshot of Buffer (showing post date):

    https://cln.sh/qzvshYXn

    • This reply was modified 21 hours, 19 minutes ago by laconicsky.
    Plugin Contributor Tim

    (@n7studios)

    18 hours, 42 minutes ago

    Is there a way to enable more verbose logging to see exactly which field Buffer is rejecting?

    Not possible, noting we report the exact error returned from Buffer’s API. If they choose not to advise which field they are rejecting, we can’t reliably tell you, either.

    As soon as a parameter is entered here the post gets submitted to Buffer.

    Correct and expected behaviour. A link status must have a URL specified in the Link field of the Plugin – for most, {url} is fine, which reflects the Page/Post being shared.

    however I have {url} in here but in buffer its showing the post date.

    A question for Buffer, noting they attempt to parse the URL to fetch its title, description and featured image for the link preview: https://www.wpzinc.com/documentation/wordpress-buffer-pro/debugging-issues/#link-posts.

    Feel free to raise support with them for further analysis here.

    istudio1991

    (@istudio1991)

    1 hour, 52 minutes ago

    I believe I may have identified a compatibility issue in WP to Buffer 6.1.0 related to Buffer’s current GraphQL schema.

    In class-wp-to-social-pro-buffer-api.php, the mutation declares:

    $assets: [AssetInput!]

    while Buffer’s current schema expects:

    $assets: [AssetInput!]!

    Additionally, the plugin only adds the assets variable when it is non-empty. For text-only posts, including some X posts, this means assets may be omitted entirely, while the current API expects a non-null list, potentially an empty array.

    A possible fix would be to:

    • initialise $assets = array();
    • always include $variables['assets'] = $assets;
    • change the GraphQL variable type to $assets: [AssetInput!]!

    This seems consistent with the generic error:

    Argument "input" has invalid value ... assets: $assets ...

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.