Procore Troubleshooting
In this article
- Home
- Observation
- Admin
- Document
- API Directory
- Missing API key
- Internal server issues within your company
- Refreshing your web browser's window/tab
- Clear your web browser's cache and delete any cookies associated with the https://app.procore.com site.
- Try reauthorizing your Procore Integration in CxAlloy
- Contact Procore Support support@procore.com.
Needed Permissions
The same user will also need CxAlloy Admin permissions that can be accessed by navigating to Account > People > Edit.
What to do when you receive an error message
500 Internal Error: The provide authorization grant is invalid, expired, revoked, does not ma (truncated…)
Description
This HTTP status code and message indicates the server encountered an error while processing your request and failed. This can be caused by several different reasons.
Possible Causes
An unexpected condition occurred
Possible Resolution
If the cause is not on the server-side (i.e. Procore's responsibility to resolve), you may be able to resolve the problem on your own by:
Client Error: GET: 403 Forbidden. ‘You do not have sufficient access to complete that action.’
Description
Users will encounter this HTTP status code and message whenever the application is attempting to perform an action it does not have privileges to access.
Possible Resolution
The single CxAlloy admin / Procore admin will need to verify the API key belongs to an enabled user with the required permissions. See diagram Procore Troubleshooting Checklist for required permissions.
For any additional questions, contact CxAlloy Support support@procore.com.
Client Error: GET: 403 Forbidden. Implicit Oauth Connections are not allow for this company
Description
The error message "Implicit Oauth Connections Are Not Allowed For This Company" means that the Company has toggled off the "Allow User Installs" option.
Possible Resolution
The app must be installed explicitly, requiring users to have to clearly ask for permission for the individual things that they want to install. The explicit installation process is outlined in the Procore Integration article on the CxAlloy support site. For any additional questions, contact CxAlloy Support support@procore.com.
Client Error: POST: 401 Unauthorized Response. The provided authorization grant is invalid, expired, revoked, does not ma (truncated…)
Description
The error message indicates the API Key is missing.
Possible Resolution
The single CxAlloy admin / Authorized Procore admin user will need disable the Procore integration for the project and re-authorized the integration between CxAlloy issues and Procore observations. For any additional questions, contact CxAlloy Support support@procore.com.
Client Error: GET: Webhook: 403 Forbidden. You do not have sufficient access to complete that action.
Description
The HTTP status code and error message indicates the application is attempting to perform an action it does not have privileges to access.
Possible Resolution
The user will need to verify your API key belongs to an enabled user with the required admin permissions. For any additional questions, contact CxAlloy Support support@procore.com.
Frequently Asked questions:
Question: Is it possible to have two different CxAlloy projects integrate with one Procore project?
Response: Yes, we recently released an update to support multiple CxAlloy projects integrating with a single Procore project.
Question: Is 'Priority' sync from CxAlloy to Procore?
Response: Yes. This is configured during the initial 'Map CxAlloy Priorities > Priority Map' setup. If a CxAlloy TQ Priority is not mapped, the corresponding Procore Observation priority will be set to 'Low'.
Question: Is there a way to mark observations from CxAlloy into Procore as 'Private'?
Response: CxAlloy integration to Procore does not have the functionality to transmit observations as private.
Question: Can checklists in CxAlloy be transmitted to Procore?
Response: No, checklist created in CxAlloy will not sync to Procore observations.
Question: In CxAlloy when an issue is created with a photo, will the photo sync to Procore?
Response: No, only comments, issues and observations are sync. Users can attach file(s), photos, etc to a Procore observation to be sync from CxAlloy to Procore.
Question: Using the Procore Integration, Is there a way to prevent unauthorized users from closing issues?
Response: As a workaround, the authorize Procore Admin/CxAlloy admin will need to create a new status in CxAlloy e.g. 'Closed in Procore - Ready for CxA Review'. During the status mapping process for the CxAlly - Procore Integration, you will need to map the new CxAlloy status to the 'Closed' status in Procore. Discussions have been made about adding an 'Ignore' or 'No Status Change' option in future updates.
Question: If I encounter a Procore Integration error that is requiring me to disable the integration and reconfigure the integration, will the process break the synchronization between the CxAlloy issues and Procore observations? Would it create duplicate observations?
Response: No. Procore observations that have already been synced will not be impacted. During the integration process, you have the option to sync older observations or not.
Question: Is CxAlloy integrated with BIM360?
Response: CxAlloy does not have an integration with BIM360, however we can copy information from Legacy BIM 360 field into CxAlloy as needed. We are currently interested in an integration with Autodesk Build, which comes from the company behind BIM 360.
Question: My former CxAlloy Admin / Procore admin is no longer with the company and I'm unable to make edits to the Procore Integration. Is there a way for me to change the user to allow me to make the needed edits?
Response: Yes. The new admin will need to disable the CxAlloy Integration to Procore and reconfigure the integration between CxAlloy and Procore. Once you complete the setup, you will need to contact CxAlloy support to move the oauth credentials from the former admin to the new admin.