Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

move troubleshoot to accordion

adilsonb21775e7e641
diff --git a/docs/documentation/platform/workflow-integrations/servicenow-integration.mdx b/docs/documentation/platform/workflow-integrations/servicenow-integration.mdx
index 6183e8534e..502b037dce 100644
--- a/docs/documentation/platform/workflow-integrations/servicenow-integration.mdx
+++ b/docs/documentation/platform/workflow-integrations/servicenow-integration.mdx
@@ -189,19 +189,41 @@ If your flow fills in **Approved By** or **Decision Notes** on the record, Infis
## Troubleshooting
-| Symptom | Cause and fix |
-| ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| A request shows **Not Submitted** in Infisical | Infisical couldn't create the record, and the reason on the request says why: the integration user's credentials or role, a missing Infisical application, or, if you self-host, a missing `SITE_URL`. Fix the cause, then select **Retry**. For connection problems, see [ServiceNow connection troubleshooting](/integrations/app-connections/servicenow#troubleshooting). |
-| A request shows **Submitting** for a long time | Infisical can't reach the instance, or the instance returns errors. Infisical keeps trying for about an hour, then closes the request. Check that the instance is up and reachable from Infisical. |
-| Record created but nothing happens | No active flow matches the record. Verify your flow is activated and its trigger condition matches the record's field values. |
-| Approvers see duplicate approvals | Two flows match the same record. Make the trigger conditions mutually exclusive and deactivate the one you no longer want. Only the first flow to finish notifies Infisical. In the other flow, **Infisical - Notify Decision** returns an error. |
-| State stuck at Notifying Infisical | The flow stopped partway through **Infisical - Notify Decision**. Check the flow's **Executions** tab in Flow Designer. |
-| Callback Failed with HTTP 403 | Infisical refused the notice because it already applied a decision to this request or closed it, the request was deleted along with its project, or ServiceNow notified Infisical about the request more than five times. Check the request's status in Infisical, and create the request again if the requester still needs access. |
-| Callback Failed with a connection error | The ServiceNow instance can't reach the **Callback URL** on the record. Fix the instance's outbound firewall rules, then select **Resend to Infisical** on the request in the **Admin Console**. If the URL itself is wrong, correct `SITE_URL` and create the request again. |
-| Callback Failed with an invalid decision | The flow passed a value other than `approved` or `rejected` to **Infisical - Notify Decision**. **Resend to Infisical** can't help, because no decision was recorded. Fix the flow, then cancel the request in Infisical and create it again. |
-| Callback Failed on a record that has no callback URL, event, or callback token | Someone created the record in ServiceNow by hand, so ServiceNow can't notify Infisical about it. Test your flows with requests made in Infisical. |
-| Request expired before approval | The policy's **Request Expiration** elapsed while the request sat in ServiceNow. Extend it, or shorten your approval SLA. |
-| Infisical says the request couldn't be completed in ServiceNow | Infisical closed the request without granting access. See [Requests closed by Infisical](#requests-closed-by-infisical). |
+<AccordionGroup>
+ <Accordion title="A request shows **Not Submitted** in Infisical">
+ Infisical couldn't create the record, and the reason on the request says why: the integration user's credentials or role, a missing Infisical application, or, if you self-host, a missing `SITE_URL`. Fix the cause, then select **Retry**. For connection problems, see [ServiceNow connection troubleshooting](/integrations/app-connections/servicenow#troubleshooting).
+ </Accordion>
+ <Accordion title="A request shows **Submitting** for a long time">
+ Infisical can't reach the instance, or the instance returns errors. Infisical keeps trying for about an hour, then closes the request. Check that the instance is up and reachable from Infisical.
+ </Accordion>
+ <Accordion title="Record created but nothing happens">
+ No active flow matches the record. Verify your flow is activated and its trigger condition matches the record's field values.
+ </Accordion>
+ <Accordion title="Approvers see duplicate approvals">
+ Two flows match the same record. Make the trigger conditions mutually exclusive and deactivate the one you no longer want. Only the first flow to finish notifies Infisical. In the other flow, **Infisical - Notify Decision** returns an error.
+ </Accordion>
+ <Accordion title="State stuck at Notifying Infisical">
+ The flow stopped partway through **Infisical - Notify Decision**. Check the flow's **Executions** tab in Flow Designer.
+ </Accordion>
+ <Accordion title="Callback Failed with HTTP 403">
+ Infisical refused the notice because it already applied a decision to this request or closed it, the request was deleted along with its project, or ServiceNow notified Infisical about the request more than five times. Check the request's status in Infisical, and create the request again if the requester still needs access.
+ </Accordion>
+ <Accordion title="Callback Failed with a connection error">
+ The ServiceNow instance can't reach the **Callback URL** on the record. Fix the instance's outbound firewall rules, then select **Resend to Infisical** on the request in the **Admin Console**. If the URL itself is wrong, correct `SITE_URL` and create the request again.
+ </Accordion>
+ <Accordion title="Callback Failed with an invalid decision">
+ The flow passed a value other than `approved` or `rejected` to **Infisical - Notify Decision**. **Resend to Infisical** can't help, because no decision was recorded. Fix the flow, then cancel the request in Infisical and create it again.
+ </Accordion>
+ <Accordion title="Callback Failed on a record that has no callback URL, event, or callback token">
+ Someone created the record in ServiceNow by hand, so ServiceNow can't notify Infisical about it. Test your flows with requests made in Infisical.
+ </Accordion>
+ <Accordion title="Request expired before approval">
+ The policy's **Request Expiration** elapsed while the request sat in ServiceNow. Extend it, or shorten your approval SLA.
+ </Accordion>
+ <Accordion title="Infisical says the request couldn't be completed in ServiceNow">
+ Infisical closed the request without granting access. See [Requests closed by Infisical](#requests-closed-by-infisical).
+ </Accordion>
+</AccordionGroup>
### Requests closed by Infisical
diff --git a/docs/integrations/app-connections/servicenow.mdx b/docs/integrations/app-connections/servicenow.mdx
index b23d5da2f1..fa2462fcc1 100644
--- a/docs/integrations/app-connections/servicenow.mdx
+++ b/docs/integrations/app-connections/servicenow.mdx
@@ -141,19 +141,23 @@ Now that your ServiceNow app connection is configured, you can use it to set up
## Troubleshooting
-| Symptom | Cause and fix |
-| --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Infisical asks you to verify the username and password of the integration user | The username or password is wrong, or the user is locked out or inactive. Check the credentials with the command after this table. |
-| Infisical says the instance URL redirected | The URL isn't the base URL of your instance, or the instance is hibernating. Wake the instance, then enter its base URL. |
-| Infisical can't reach the instance | The instance URL is wrong, or the instance blocks traffic from Infisical. Allow [Infisical's IP addresses](/documentation/setup/networking) on the instance's IP access control list. |
-| An access request shows **Not Submitted**, and its reason says the instance has no Infisical Approvals application endpoint | The Infisical application isn't installed or active on the instance. Install it, then select **Retry** on the request. |
-| An access request shows **Not Submitted**, and its reason says the instance rejected the integration user's credentials | The integration user's password changed, or the user doesn't have the `x_infis_approvals.secret-manager-integration` role. Update the connection or the user, then select **Retry** on the request. |
-| Infisical won't delete the connection | An access policy still uses the connection. Select another connection on the policy, or switch the policy back to Infisical approvals, then delete the connection. |
-
-A web service user can't sign in to the ServiceNow UI, so check its credentials from the command line instead:
-
-```bash
-curl -u '<username>:<password>' https://<instance>.service-now.com/api/now/ui/user/current_user
-```
-
-If the username and password work, ServiceNow returns a `200` response with the integration user's details.
+<AccordionGroup>
+ <Accordion title="Infisical asks you to verify the username and password of the integration user">
+ The username or password is wrong, or the user is locked out or inactive.
+ </Accordion>
+ <Accordion title="Infisical says the instance URL redirected">
+ The URL isn't the base URL of your instance, or the instance is hibernating. Wake the instance, then enter its base URL.
+ </Accordion>
+ <Accordion title="Infisical can't reach the instance">
+ The instance URL is wrong, or the instance blocks traffic from Infisical. Allow [Infisical's IP addresses](/documentation/setup/networking) on the instance's IP access control list.
+ </Accordion>
+ <Accordion title="An access request shows **Not Submitted**, and its reason says the instance has no Infisical Approvals application endpoint">
+ The Infisical application isn't installed or active on the instance. Install it, then select **Retry** on the request.
+ </Accordion>
+ <Accordion title="An access request shows **Not Submitted**, and its reason says the instance rejected the integration user's credentials">
+ The integration user's password changed, or the user doesn't have the `x_infis_approvals.secret-manager-integration` role. Update the connection or the user, then select **Retry** on the request.
+ </Accordion>
+ <Accordion title="Infisical won't delete the connection">
+ An access policy still uses the connection. Select another connection on the policy, or switch the policy back to Infisical approvals, then delete the connection.
+ </Accordion>
+</AccordionGroup>