matt
/
port-nimara-client-portal
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updates

This commit is contained in:
Matt 2025-06-10 00:04:24 +02:00
parent 2da6c06aab
commit b391db0253
1 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/email-system-fixes.md
View File

@ -81,25 +81,22 @@
- Added "Waiting for Signatures" as option 2 in EOI Status - Added "Waiting for Signatures" as option 2 in EOI Status
- New order: "Awaiting Further Details" → "Waiting for Signatures" → "Signed" - New order: "Awaiting Further Details" → "Waiting for Signatures" → "Signed"
### 11. 404 Errors for Existing Records During Updates ### 11. 404 Errors for Existing Records During Updates - FIXED
- **Problem**: Records that exist in the database return 404 when trying to update them - **Problem**: Records that exist in the database return 404 when trying to update them
- **Root Cause**: The update request was including webhook objects in the body that shouldn't be sent
- **Solution**: - **Solution**:
- Added verification step to first try fetching the record before updating - Now skipping all object fields (including webhook fields) during updates
- Only sending primitive values (strings, numbers, nulls) to the API
- Removed webhook fields from the allowed fields list
- Added retry mechanism with exponential backoff (3 retries with 1s, 2s, 3s delays) - Added retry mechanism with exponential backoff (3 retries with 1s, 2s, 3s delays)
- Enhanced logging to show exact URLs, headers, and request bodies - 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:** **Fixed webhook fields that were causing the issue:**
1. Verify record exists with GET before attempting PATCH - "Request More Information" (webhook object)
2. Log complete request details including URLs and tokens - "Request More Info - To Sales" (webhook object)
3. Retry with exponential backoff in case of timing issues - "EOI Send to Sales" (webhook object)
**If the issue persists:** These fields are now automatically filtered out during updates, preventing the 404 errors.
- 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 ## Required Environment Variables