Error: 400 on Salesforce HTTP request and Error: 0 when pulling Opportunity data

  • Resolved zumajoe

    (@zumajoe)


    4 years, 8 months ago

    Hi there,

    I’m also experiencing the Error: 400: on Salesforce HTTP request, which seems exactly the same issue as this post: https://www.ads-software.com/support/topic/got-error-400-on-salesforce-http-request/

    and also this one:
    https://www.ads-software.com/support/topic/extra-comma-in-soql/

    Why it’s adding an extra comma to the SOQL and also trying to query “Speaker_Bio__c” makes no sense since it’s not even in my Fieldmaps anymore as you can see, and all cache has been cleared.

    Below are some screenshots uploaded to ImgBB:

    WP Fieldmaps Settings
    https://ibb.co/p3Rq7sh

    Error 400
    https://ibb.co/PZKqfjn

    Error 0
    https://ibb.co/GcHHSPr

    I’ve done the following:

    • Ensured there are no Filters enabled
    • Deleted all Fieldmaps and started over
    • Modified scheduling frequency
    • Cleared scheduling queue
    • Deleted all Fieldmaps and started over
    • Changed fieldmaps with different field requests
    • Verified correct API version
    • Cleared plugin cache, server cache, etc.

    WordPress Version: 5.3.2
    Plugin Version: 1.8.12
    PHP Version: 7.3

    Is there a way to manually view / clear the cache? Any additional information on how to resolve this would be very helpful.

    Thanks!

    • This topic was modified 4 years, 8 months ago by zumajoe.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter zumajoe

    (@zumajoe)

    I found that this was caused from an entry in the database within the wp_options table:

    object_sync_for_salesforce_currently_pulling_query_Opportunity

    Once I deleted this row, boom issue resolved. Is this supposed to be cleared by cache? How can we prevent this from happening in the future without needing to manually edit our database?

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    @zumajoe thanks for this info. I think it might be a bug. Would you mind creating a bug report with this information? The next version is in progress, but it’s much larger changes. I’m willing to release a small update with this, if it is a bug we can duplicate and also if deleting this row would be a fix that doesn’t cause other issues.

    Plugin Author Jonathan Stegall

    (@jonathanstegall)

    I believe I have a fix for this. I’ll be releasing an update with this fix shortly (and hopefully still a larger update eventually).

    You can test the fix at https://github.com/MinnPost/object-sync-for-salesforce, if you like. It’s in the master branch now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error: 400 on Salesforce HTTP request and Error: 0 when pulling Opportunity data’ is closed to new replies.