> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/troubleshooting/delpha-salesforce-connection-and-permission-errors.md). # Delpha Salesforce Connection & Permission Errors Fix common Delpha Salesforce errors including stuck "Sent" records, missing authorization, trigger configuration issues, and credential access errors with step-by-step solutions. If something goes wrong, Delpha shows you the reason on screen. Here is what each message means. ### Records stay in "Sent" and no results ever arrive Nothing is shown on screen, because from Salesforce's point of view nothing went wrong — Delpha received the request and did the work, but could not write the answer back. * the integration user has no Delpha licence, which makes the whole package invisible to it. Setup → Installed Packages → Delpha → Manage Licenses, and check your integration user is listed. Add it, then re-run the assessment — you do not need to reconnect. * If the licence is already assigned, check if the integration user has the *Delpha User **Permission Group** (or data steward or admin)* ), and check that the user still holds the **Delpha Integration User** permission set — Delpha assigns it at Connect, and it is what lets Delpha's answers reach your org. If it is missing, press Connect again. [.](mailto:support@delpha.io) ### A Salesforce administrator must authorize the Delpha app [External App Setup](/delpha-for-salesforce/delpha-setup/install-delpha/connect-the-org-to-delpha.md) was not completed, or was completed on the wrong app. Re-check that: * Permitted Users is set to *Admin approved users are pre-authorized* * the profile of the Delpha Integration user you picked is in the app's pre-authorised list — or, if you took the permission set route, that Delpha Integration permission set is in that list *and* assigned to exactly that user Then press Connect again. ### Connected, but this user cannot configure the Delpha platform event triggers Check if the 3 mandatories permissions are ticked in the profile used for the Delpha Integration User. Go back to Setup → Users → Profiles → your integration user's profile → System Permissions → Edit, and confirm all three are ticked: *Customize Application*, *View All Data*, *View Setup and Configuration*. Save, then press connect again. ### This org is still connected with the previous method **Solution** You upgraded from an older Delpha version (pre 3.91.x) and have not reconnected yet. Nothing is broken — Delpha keeps working. When convenient, move to[ the new connection](/delpha-for-salesforce/delpha-setup/install-delpha/connect-the-org-to-delpha.md), which does not expire and does not need periodic re-authorisation. ### We couldn't access the credential(s)... the external credential might not exist This is about **your account**, not the integration user's. Assign yourself the Delpha Admin Permission Group, then press Connect again. If you did assign it, give the permission set group a minute to recalculate and press Connect again — a group that is still recalculating grants nothing yet. **Anything else** Take a screenshot of the message — it includes a reference code — and send it to --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.delpha.io/delpha-for-salesforce/troubleshooting/delpha-salesforce-connection-and-permission-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.