Messages for services and at the relay

Messages from “My services”, “Services” and the relay log.

“The services could not be loaded.”

• Cause: The list of connections could not be fetched. If the message shows “HTTP 404”, this system does not know the services feature yet – it is being enabled step by step.
• Fix: Reload. If it stays at 404, the relay is not active on this system yet; the “Connect GitHub” card only works after that.

“The resources could not be fetched.”

• Cause: The connected service did not answer the request for its resources (repositories, folders), or access was revoked at the service.
• Fix: Check at the service whether relais.io is still authorised; otherwise “Disconnect” and reconnect.

“The permissions could not be loaded.”

• Cause: Permissions per agent are visible only to whoever may decide in the responsible unit.
• Fix: Check permissions; personal services have no permissions – they apply to your own agents.

“Personal services are blocked here.” / “Blocked”

• Cause: Not an error: this company workspace does not allow personal services. Management decided so.
• Fix: Have the service connected as a workspace service (“Services”) – then with permissions per agent.

Access “denied” in the relay log

• Cause: Not an error: the agent called a tool that is not permitted (for example “delete files”). The relay stopped the call and told the agent why.
• Fix: If the access is wanted: extend the permission at the service. If not: nothing – that is exactly what the relay is for.

“Effective immediately: the next call will be denied at the relay.”

• Cause: Not an error, a confirmation: you are about to remove a permission.
• Fix: Confirm if intended. The row in the log stays – so it remains traceable what the agent was allowed until then.