All systems operational

Integration Failed

Diagnose a failing integration — usually incorrect details, a permissions issue, or a connector that is not fully available.

#Purpose

Restore a broken connection.

#When to use this

When connecting or testing an integration fails.

#At a glance

DetailValue
Required permissionsManage integrations (CEO or admin)
Administrator levelCEO / Admin
Portal areas usedIntegrations, Status checks

#Step by step

1

Re-check details

Confirm credentials and URLs are correct.
2

Run the connection test

See the exact failure.
3

Check availability

Confirm the connector is live, not Planned/Coming Soon.
4

Reconnect

Remove and re-add the connection if needed.

#Approval points

No formal approval gate

This administrative action does not require a separate sign-off, but review carefully before applying changes.

#Security notes

Security considerations

  • Handle integration credentials carefully.
  • Restrict who can change integration settings.

#Best practices

  • Test after connecting.
  • Confirm availability before relying on a connector.

#Common mistakes

  • Typos in credentials or URLs.
  • Expecting an unavailable connector to work.

#Troubleshooting

If this happensTry this
The test keeps failingRe-enter credentials carefully and confirm the connector is live; contact support if it persists.

#FAQ

Could the connector simply be unavailable?

Yes — confirm it is live and not Planned/Coming Soon.

#Keep exploring

#Business modules & workflows

Still need help?

Can’t find what you’re looking for? The DevSphere OS team is happy to help.