This box may not use your org's credential here
Code: egress.no_grant
What happened
Section titled “What happened”The box’s policy may not use the org’s credential for the destination.
Awake’s answer says:
the box's policy doesn't let it use your org's credential for this destinationWhy Awake does this
Section titled “Why Awake does this”Every request a box sends leaves through the Egress Proxy, outside the box, which allows only what your org’s policy names and refuses the rest. The Egress Proxy says more.
What you can do
Section titled “What you can do”Ask your Awake admin to let your box use the org’s credential for this destination.
What your admin can do
Section titled “What your admin can do”In the console, an Org admin opens Admin → Secrets.
For agents
Section titled “For agents”Tell the person what was refused and why, with this code, and don’t retry in a loop. Don’t try another host, encoding or route to get around a control.
Where Awake records it
Section titled “Where Awake records it”The Egress Proxy records each refusal, never the request’s data. Org admins and security auditors read the records in the Audit log.
Related codes
Section titled “Related codes”egress.credential_in_query: A credential was sent in the URLegress.credential_unavailable: The proxy couldn’t get your org’s credential
Still stuck
Section titled “Still stuck”Ask your Awake admin. Give them the code, egress.no_grant, and when it happened.