✖ Indexing is still in progress | Trigger.dev | Page 1

woeful zinc May 14, 2024, 7:49 AM

#

I've been getting this error locally for the past couple of hours.
CLI command: npx @trigger.dev/cli@latest dev

iron sun May 14, 2024, 8:41 AM

#

Is this still happening for you? Have you made any code changes? The API is responding normally so this is unexpected

woeful zinc May 14, 2024, 8:48 AM

#

Yes still happening, Yes I've done code changes locally then I've built the project and encountered no issues.

#

iron sun May 14, 2024, 8:50 AM

#

If you stash your changes and rollback do you still get this error?

woeful zinc May 14, 2024, 8:57 AM

#

I'll try

If there are any code issues, is there a way to log(error logs) them?

iron sun May 14, 2024, 9:33 AM

#

The errors should appear in your main app logs. Where you run npm run dev

woeful zinc May 14, 2024, 10:43 AM

#

There were no errors in the main app logs. The problem was solved just after running the command in an new external terminal. I assume it happened due to a caching issue. Thanks for the reply.

topaz forge May 14, 2024, 12:21 PM

#

^ having the same issue rn

topaz forge May 14, 2024, 12:28 PM

#

iron sun If you stash your changes and rollback do you still get this error?

also tried that but still persists

iron sun May 14, 2024, 1:23 PM

#

@topaz forge can you share your org name?

topaz forge May 14, 2024, 1:26 PM

#

iron sun <@538823751555612672> can you share your org name?

works flawless now, i guess a downtime?

iron sun May 14, 2024, 1:30 PM

#

There's been no downtime that's been detected by our every 5 second healthcheck. I get a very loud alarm when that happens. It could be a specific issue related to indexing v2 projects though

#✖ Indexing is still in progress