This commit is contained in:
2025-06-09 23:42:31 +02:00
parent 2f1f970267
commit cc2cc282b9
3 changed files with 60 additions and 14 deletions

View File

@@ -81,14 +81,25 @@
- Added "Waiting for Signatures" as option 2 in EOI Status
- New order: "Awaiting Further Details" → "Waiting for Signatures" → "Signed"
### 11. 404 Errors for Newly Created Records
- **Problem**: Newly created records sometimes show 404 when immediately updating/linking
### 11. 404 Errors for Existing Records During Updates
- **Problem**: Records that exist in the database return 404 when trying to update them
- **Solution**:
- Added retry mechanism with exponential backoff to `updateInterest` function
- Will retry up to 3 times with increasing delays (1s, 2s, 3s)
- `get-interest-berths` returns empty list instead of throwing error for new records
- This handles NocoDB synchronization delays where records need time to propagate
- After 3 retries, provides detailed error message explaining possible causes
- Added verification step to first try fetching the record before updating
- Added retry mechanism with exponential backoff (3 retries with 1s, 2s, 3s delays)
- Enhanced logging to show exact URLs, headers, and request bodies
- Added Content-Type header to PATCH requests
- `get-interest-berths` returns empty list instead of throwing error for 404s
**Investigation Steps Added:**
1. Verify record exists with GET before attempting PATCH
2. Log complete request details including URLs and tokens
3. Retry with exponential backoff in case of timing issues
**If the issue persists:**
- Check if the NocoDB API token has write permissions
- Verify the table ID hasn't changed
- Try updating a different record to see if it's record-specific
- Check NocoDB logs for more details about the 404 error
## Required Environment Variables