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
Notice that scheduled task was NOT created which is unexpected as it was just deleted one step ago and so using same Upstash-Deduplication-Id should be allowed.
Same happens with Upstash-Content-Based-Deduplication: true
The text was updated successfully, but these errors were encountered:
privet-fun
changed the title
Odd Upstash-Deduplication-Id / Upstash-Content-Based-Deduplication behavior
Unexpected Upstash-Deduplication-Id / Upstash-Content-Based-Deduplication behavior
Jul 23, 2023
I'm running into the same issue, can I recreate the schedule with the same Deduplication ID if it's already deleted? @chronark, is there any option to remove it from the cache?
Steps to reproduce:
1: Create new scheduled tast:
POST https://qstash.upstash.io/v1/publish/<my_webworker_url>
Headers
Upstash-Cron: * * * * *
Upstash-Deduplication-Id: abcd
Response: HTTP 201 Created
Body: { "scheduleId": "scd_uniqueId" "}
2: Verify that deduplication is working by repeating step 1
Response: HTTP 202 Accepted
3: Delete schedule
DELETE https://qstash.upstash.io/v1/schedules/scd_uniqueId
Response: HTTP 202 Accepted
Body: { "status": "accepted" }
4: Go to https://console.upstash.com/qstash?tab=details and verify that scheduled task deleted
5: Attempt to create new schedule task as in step 1
Response: HTTP 202 Accepted
Body: { "scheduleId": "scd_uniqueId" "}
Notice that scheduled task was NOT created which is unexpected as it was just deleted one step ago and so using same Upstash-Deduplication-Id should be allowed.
Same happens with Upstash-Content-Based-Deduplication: true
The text was updated successfully, but these errors were encountered: