Inbound Requests
Inbound logs every request a gateway made to the ERP, whether it was accepted or refused. It is the connection-level view: before asking why an event did not turn into an attendance record, this is where you confirm the request arrived at all.
Where to find it
Go to EdgeBridge > Inbound.
What the list shows
| Column | Description |
|---|---|
| When / Date | When the request arrived. |
| Gateway | Which gateway made it. |
| From IP | The address it came from. |
| Endpoint | What it called. |
| HTTP | The status returned. |
| Result | accepted, rejected or duplicate. |
| Events | How many events the request carried. |
| Took | How long it took to handle. |
| Error | Why it was refused, where it was. |
Reading the result
| Result | What it means | What to do |
|---|---|---|
| accepted | The payload was taken. Whether it became anything is a separate question. | Follow it in Events. |
| rejected | Refused — bad key, unlisted IP, or rate limit. | Check the key and allowed IPs on Gateways. |
| duplicate | The same payload was already received. | Nothing. This is the retry logic working. |
Duplicates are healthy. A gateway that loses its connection mid-send retries, and the ERP recognising the repeat is what stops one punch becoming two attendance records.
When nothing appears at all
An empty Inbound list means the gateway is not reaching the ERP. That is a network, URL or service problem on the gateway machine — not a permissions or mapping problem in the ERP, because a refused request would still be logged here.
Retention
The request log is trimmed on the schedule set in Settings. It is diagnostic data, so keep enough days to cover a weekend but no more than you will read.