.png){kind=logo}
SFDC Connection Error: Unable to Run Validation Explained
Hi There, My SFDC connection is saying "Error - Unable to run validation" but up until today, there haven't been any issues with my SFDC connection.
There could be a few reasons for the "Error - Unable to run validation" message with your Salesforce connection. Here are some steps to troubleshoot: 1. Check if your API credits have run out. If so, you'll need to purchase additional credits from your provider. 2. Try logging out of your account and performing a hard refresh of your browser: • On Mac: Press Cmd + Shift + R (Chrome/Firefox) or Cmd + Option + R (Safari) • On PC: Press Ctrl + F5 (Chrome/Firefox/Edge) • Then log back in. 3. Verify that your API key is correct and has all necessary permissions. If these steps don't resolve the issue, please request human assistance by clicking on "Talk to a person" for further support.
Kyle P.··I came here to say the same thing. This may be a bug?
The "Error - Unable to run validation" with your SFDC connection might not be a bug, but rather an issue that can be resolved. Here are some steps to try: 1. Log out of your account and perform a hard refresh of your browser: • On Mac: Press Cmd + Shift + R (Chrome/Firefox) or Cmd + Option + R (Safari) • On PC: Press Ctrl + F5 (Chrome/Firefox/Edge) 2. Log back in and try connecting again. 3. If the issue persists, check if your API credits have run out. You may need to purchase additional credits. 4. Verify that your API key is correct and has all necessary permissions. If these steps don't resolve the issue, please request human assistance by clicking on "Talk to a person" for further support.
Not a table but integration error. I followed the hard reset and that didn't work. Looks like there is another user expericing this issue as well.
Bruno R.··Hey there, sorry for this, it looks like we're having some trouble with our SFDC actions. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
- Bruno R.··
This issue should since have been mitigated - let me know if you're able to run these actions now!