You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Revert attempt_metadata → delivery_metadata in OpenAPI (matches Go code)
- Fix config: delivery_prefix → attempt_prefix, example att → atm
- Fix variable names: deliveryID → attemptID, attErr → atmErr
- Fix test names: TestListDeliveries → TestListAttempts, etc.
- Update doc links for renamed API endpoints
- Update comments and test descriptions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/pages/guides/building-your-own-ui.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -372,6 +372,6 @@ return (
372
372
);
373
373
```
374
374
375
-
For each event, you can retrieve all its associated delivery attempts using the [List Event Deliveries Attempts API](/docs/api/event-deliveries-attempts#list-event-deliveries-attempts).
375
+
For each event, you can retrieve all its associated delivery attempts using the [List Event Attempts API](/docs/api/events#list-event-attempts).
376
376
377
377
You can find the source code of the `Events.tsx` component of the User Portal here: [Events.tsx](https://github.com/hookdeck/outpost/blob/main/internal/portal/src/scenes/Destination/Events/Events.tsx)
Copy file name to clipboardExpand all lines: docs/pages/guides/migrate-to-outpost.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,7 +129,7 @@ To migrate your historical data to Outpost, you need to map your existing data s
129
129
The Outpost schema contains two tables related to events:
130
130
131
131
1.**events** - The events that Outpost has received to publish.
132
-
2.**deliveries** - The delivery attempts of events to destinations.
132
+
2.**attempts** - The delivery attempts of events to destinations.
133
133
134
134
The following diagram shows the Outpost schema. You can connect to the database instance within your Outpost installation to inspect the schema further.
Copy file name to clipboardExpand all lines: docs/pages/references/configuration.mdx
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Global configurations are provided through env variables or a YAML file. ConfigM
74
74
|`GCP_PUBSUB_SERVICE_ACCOUNT_CREDENTIALS`| JSON string or path to a file containing GCP service account credentials for Pub/Sub. Required if GCP Pub/Sub is the chosen MQ provider and not running in an environment with implicit credentials (e.g., GCE, GKE). |`nil`| Conditional |
75
75
|`GIN_MODE`| Sets the Gin framework mode (e.g., 'debug', 'release', 'test'). See Gin documentation for details. |`release`| No |
76
76
|`HTTP_USER_AGENT`| Custom HTTP User-Agent string for outgoing webhook deliveries. If unset, a default (OrganizationName/Version) is used. |`nil`| No |
77
-
|`IDGEN_DELIVERY_PREFIX`| Prefix for delivery IDs, prepended with underscore (e.g., 'dlv_123'). Default: empty (no prefix) |`nil`| No |
77
+
|`IDGEN_ATTEMPT_PREFIX`| Prefix for attempt IDs, prepended with underscore (e.g., 'atm_123'). Default: empty (no prefix) |`nil`| No |
78
78
|`IDGEN_DESTINATION_PREFIX`| Prefix for destination IDs, prepended with underscore (e.g., 'dst_123'). Default: empty (no prefix) |`nil`| No |
79
79
|`IDGEN_EVENT_PREFIX`| Prefix for event IDs, prepended with underscore (e.g., 'evt_123'). Default: empty (no prefix) |`nil`| No |
80
80
|`IDGEN_TYPE`| ID generation type for all entities: uuidv4, uuidv7, nanoid. Default: uuidv4 |`uuidv4`| No |
@@ -133,6 +133,7 @@ Global configurations are provided through env variables or a YAML file. ConfigM
133
133
|`RETRY_INTERVAL_SECONDS`| Interval in seconds for exponential backoff retry strategy (base 2). Ignored if retry_schedule is provided. |`30`| No |
134
134
|`RETRY_POLL_BACKOFF_MS`| Backoff time in milliseconds when the retry monitor finds no messages to process. When a retry message is found, the monitor immediately polls for the next message without delay. Lower values provide faster retry processing but increase Redis load. For serverless Redis providers (Upstash, ElastiCache Serverless), consider increasing to 5000-10000ms to reduce costs. Default: 100 |`100`| No |
135
135
|`RETRY_SCHEDULE`| Comma-separated list of retry delays in seconds. If provided, overrides retry_interval_seconds and retry_max_limit. Schedule length defines the max number of retries. Example: '5,60,600,3600,7200' for 5 retries at 5s, 1m, 10m, 1h, 2h. |`[]`| No |
136
+
|`RETRY_VISIBILITY_TIMEOUT_SECONDS`| Time in seconds a retry message is hidden after being received before becoming visible again for reprocessing. This applies when event data is temporarily unavailable (e.g., race condition with log persistence). Default: 30 |`30`| No |
136
137
|`SERVICE`| Specifies the service type to run. Valid values: 'api', 'log', 'delivery', or empty/all for singular mode (runs all services). |`nil`| No |
137
138
|`TELEMETRY_BATCH_INTERVAL`| Maximum time in seconds to wait before sending a batch of telemetry events if batch size is not reached. |`5`| No |
138
139
|`TELEMETRY_BATCH_SIZE`| Maximum number of telemetry events to batch before sending. |`100`| No |
@@ -269,8 +270,8 @@ gin_mode: "release"
269
270
http_user_agent: ""
270
271
271
272
idgen:
272
-
# Prefix for delivery IDs, prepended with underscore (e.g., 'dlv_123'). Default: empty (no prefix)
273
-
delivery_prefix: ""
273
+
# Prefix for attempt IDs, prepended with underscore (e.g., 'atm_123'). Default: empty (no prefix)
274
+
attempt_prefix: ""
274
275
275
276
# Prefix for destination IDs, prepended with underscore (e.g., 'dst_123'). Default: empty (no prefix)
276
277
destination_prefix: ""
@@ -607,6 +608,9 @@ retry_poll_backoff_ms: 100
607
608
# Comma-separated list of retry delays in seconds. If provided, overrides retry_interval_seconds and retry_max_limit. Schedule length defines the max number of retries. Example: '5,60,600,3600,7200' for 5 retries at 5s, 1m, 10m, 1h, 2h.
608
609
retry_schedule: []
609
610
611
+
# Time in seconds a retry message is hidden after being received before becoming visible again for reprocessing. This applies when event data is temporarily unavailable (e.g., race condition with log persistence). Default: 30
612
+
retry_visibility_timeout_seconds: 30
613
+
610
614
# Specifies the service type to run. Valid values: 'api', 'log', 'delivery', or empty/all for singular mode (runs all services).
0 commit comments