Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get messages older than 12 hours #1455

Closed
n3xt-samuel opened this issue Sep 28, 2024 · 3 comments
Closed

Unable to get messages older than 12 hours #1455

n3xt-samuel opened this issue Sep 28, 2024 · 3 comments
Assignees
Labels
cloud The hosted Svix service server Issues regarding the server component

Comments

@n3xt-samuel
Copy link

Bug Report

Version

svix npm package v1.26.0

Platform

N/A

Description

I am using the svix package to get messages and noticed that I am unable to fetch messages older than 12 hours old (may be shorter).

I am able to query new messages.

Org name: n3xt
App Id: app_2mZbzzog8mEKxDMN3851uyMlym0

Screenshot 2024-09-28 at 2 26 46 PM

For example I am able to query for fb3aa742-da1d-4749-8fd7-54256fc64ccc but when I query for 5b99d7b3-5342-4da8-95c5-41a3b4d1514f, I get this in the response

Message: {"code":"not_found","detail":"message not found"}

Snippet

await svix.message.get("app_2mZbzzog8mEKxDMN3851uyMlym0", "fb3aa742-da1d-4749-8fd7-54256fc64ccc")); // Good
await svix.message.get("app_2mZbzzog8mEKxDMN3851uyMlym0", "5b99d7b3-5342-4da8-95c5-41a3b4d1514f"); // Not Found

What I expect

I should be able to query older messages.

What is happening

I am unable to query messages older than 12 hours.

@tasn tasn added the server Issues regarding the server component label Sep 28, 2024
@tasn
Copy link
Member

tasn commented Sep 28, 2024

Thanks for reporting, we'll take a look!

@tasn tasn added the cloud The hosted Svix service label Sep 28, 2024
@svix-gabriel svix-gabriel self-assigned this Sep 30, 2024
@svix-gabriel
Copy link
Contributor

I took a look into this, but I haven't been able replicate the issue.

These are the steps I took to reproduce

  1. Created a Message with an eventId
  2. Called GET /api/v1/app/:app_id/msg/:id using the eventId from step 1. The message returned successfully.
  3. A bit over 12h later, I called GET /api/v1/app/:app_id/msg/:id, again using the same eventId. The message returned successfully.

I also couldn't find anything in the code that would indicate the bug you described. Are the steps I took to reproduce accurate? Is there any other info about the message that might be relevant? (For example, did the message have a payload that expired or was manually deleted?).

@n3xt-samuel
Copy link
Author

Thank you for the quick investigation @svix-gabriel. Weirdly, I'm able to get the above messages that failed before. I'll close the issue for now since I can't repro it anymore.

@n3xt-samuel n3xt-samuel closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud The hosted Svix service server Issues regarding the server component
Projects
None yet
Development

No branches or pull requests

3 participants