Procore - Help and Troubleshooting
In this article, we’ll walk through the most common Procore–Part3 connection issues and how to quickly fix them 🙌
You’ll find solutions for:
- Trouble returning a submittal or RFI
- Missing or outdated submittals/RFIs
- Error pop-ups during syncing
- “404 error” when clicking View in Procore
Trouble Returning a Submittal or RFI
If you're responding to a submittal or RFI but you can't return it, there can be a couple of reasons.
Reason #1: Make sure you've authorized your connection.
To return something to Procore, they want to make sure you're the right person. Check out this article on how to 'Authorize your account'.

Reason #2: You must be the person who has the Ball in Court to see a 'Return to Procore' button.

If you're added as a collaborator, you will see the option to send your response to the person who owns the step (aka, the person who asked you to collaborate).
We also recommend using the comments section at the bottom of the page to @ mention the person to let them know you're done 👍
Reason #3: You may need to re-enter your RFI response, then hit return again.
On the rare chance that you have the ball-in-court, but aren't able to return the RFI, you may need to add a new response. Sometimes Procore has already synced the response and will not accept the same response.
In this scenario, add a new response such as 'Refer to the response above' or similar.

Note: When consultants return a submittal or RFI the status bar in the top right corner will move to 'Returned'. Only the general contractor who owns the Procore project can shift the status to 'Closed'
Missing or Outdated Submittal or RFI
If you ever notice that you're missing submittals or RFIs, there are a few reasons why it could be happening, and a few different ways to fix it.
Reason #1: Your logs may not be synced.
The logs sync automatically when there are updates to Procore, however, if you experience an issue you can force the sync.
To do this, click the 'sync' button in the top right corner of the main logs page. This will trigger Part3 to run a check in the background to make sure Part3 has the latest and greatest submittals/RFIs.

Reason #2: Your document may not be synced.
If the GC tells you they updated a submittal or RFI, but you don't see the update...click the 'sync' button in the top right screen, within the document.
This type of sync is document-specific (unlike syncing at the logs page). This will pull in all of the latest documents, steps, wording, etc...

Reason #3: You can see a submittal/RFI in Procore but not Part3
If you can see a submittal or RFI in Procore but not Part3, try syncing your logs as mentioned in option 1 here. If nothing changes, reach out to support@part3.io
To help us troubleshoot this quickly for you, please copy and paste the URL from Procore into the message you send us. This will help us track down the missing document.

Receiving an Error
If you receive an error message when returning a submittal or RFI, please reauthorize your account.
Step 1: Go to your Account Settings (initials top right corner)
Step 2: Scroll down to 'Integrations'.
- Option 1: Click the blue 'reauthorize' button
- Option 2: Click the red 'revoke' button and make the connection again. Don't worry, you won't lose any information or data by revoking and reconnecting!


“404 Error” When Clicking View in Procore
The Procore URL has changed over the years as Procore has grown. This means that their URLs aren't consistent across projects.
If you experience a 404 error when clicking 'View in Procore', follow the steps below:
Step 1: Go to 'Project Settings' and select 'Integrations'

Step 2: When you view your project in Procore, check what the prefix URL is before the ".procore.com". Click the edit icon to update the URL in Part3.


***Note, that you only need to update the characters before ".procore.com"
Only Prime Consultants and the individual who established the connection have this functionality
As always, if you have any questions or see any issues with this article, please reach out to us at support@part3.io