Skip to content
Awake docs

Brain Sync's route refused the request

Code: egress.brain_path

What happened

Section titled “What happened”

A request on Brain Sync’s route wasn’t one of the creates Brain Sync makes.

Awake’s answer says:

Brain Sync's route takes only its owner's chunk and manifest creates, as Brain Sync makes them

Why 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”

Nothing to do here, since only Brain Sync uses this route. If sync keeps failing, contact support.

What your admin can do

Section titled “What your admin can do”

Nothing in the console changes this: your admin can ask Awake support.

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.

Section titled “Related codes”

Still stuck

Section titled “Still stuck”

Your Awake admin can ask Awake support. Give them the code, egress.brain_path, and when it happened.