Skip to main content
Use Execution Context Search when you know a business value but do not know the execution ID. For example, you may know:
  • customer ID
  • user ID
  • request ID
  • order ID
  • transaction ID
  • reference number
  • response status
  • provider reference
Foveus can use indexed context fields to find the execution that contains that value.

​
Example

A customer contacts support and says their order failed. You know: Search:
This returns executions from orders-api where Foveus indexed customerId = cus_12345.

​
Query format

Use the context: token.
For example:
When you know the service, include it:
Adding a service filter keeps the search faster and more precise.

​
Use quotes for strings

String values should use quotes.
Numbers do not need quotes.
Booleans do not need quotes.

​
Search by request ID

If your service captures request IDs, search by request ID.
Foveus normalizes common key styles, so these can resolve to the same indexed key when captured:
This helps when different teams or providers use different naming conventions.

​
Search by nested values

Use dotted paths for nested context. Given this response:
Search by numeric value:
Search by label:

​
Search by multiple values

Use commas when you want to search for more than one value for the same key.
Values for the same key use OR. This means:

​
Search by multiple keys

Use multiple context: tokens when you want all conditions to match.
Different keys use AND. This means:

​
Add status when needed

If you are looking for a failure, add status:failed.
This narrows the search to failed executions for that customer.

​
Add endpoint when known

If you know the endpoint, add it.
This is useful when the same business ID appears across multiple endpoints.

​
What Foveus searches

Foveus searches indexed execution context. Context can come from:
  • request query
  • request body
  • response body
  • custom context
Foveus does not scan arbitrary raw request or response bodies.

​
If no result appears

Check the following:

​
The service name matches

Search by the service name shown in Foveus.
If your organization uses environment-specific service names, search by the actual name your service sends.

​
The value is quoted if it is a string

Use:
not:

​
The value was captured

Open a nearby execution and confirm the request or response context includes the value.

​
The field was indexed

Execution Context Search only works on indexed context fields. If indexing settings changed recently, trigger a new request and search again.

​
The route was not excluded

If the endpoint is excluded by SDK configuration, Foveus may not capture the execution or context. Check:

​
The execution is still within retention

Searchable context follows execution retention. If the execution expired, its searchable context expires too.
  1. Start with service:.
  2. Add the business ID with context:.
  3. Add status:failed if you are investigating a failure.
  4. Add method: and endpoint: if you know the route.
  5. Open the execution.
  6. Inspect response context, timeline, and logs.

​
More examples

Find by customer ID:
Find by user ID:
Find by request ID:
Find by transaction ID:
Find failed executions for an order:
Find an execution with a confirmed order status:

​
What to do next