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
ERROR: relation "public.Epoch" does not exist at character 288
2025-01-22 07:19:54.487 UTC [80] STATEMENT: SELECT coalesce(json_agg("root" ORDER BY "root.pg.number" DESC NULLS FIRST), '[]' ) AS "root" FROM (SELECT row_to_json((SELECT "_e" FROM (SELECT "_root.base"."number" AS "number" ) AS "_e" ) ) AS "root", "_root.base"."number" AS "root.pg.number" FROM (SELECT * FROM "public"."Epoch" WHERE ('true') ORDER BY "number" DESC NULLS FIRST LIMIT 1 ) AS "_root.base" ORDER BY "root.pg.number" DESC NULLS FIRST ) AS "_root"
2025-01-22 07:19:54.586 UTC [79] ERROR: relation "public.TokenMint" does not exist at character 154
2025-01-22 07:19:54.586 UTC [79] STATEMENT: SELECT json_build_object('aggregate', json_build_object('count', COUNT(*) ) ) AS "root" FROM (SELECT 1 FROM (SELECT DISTINCT ON ("assetId") * FROM "public"."TokenMint" WHERE ('true') ) AS "_root.base" ) AS "_root"
@aobalv123 sorry for the late reply. This looks like the background service is having troubles to start. Since these tables will be created on startup.
Could you share the logs from the background service?
And additionally if you see anything else suspicios in other services it will help as well.
ERROR: relation "public.Block" does not exist at character 850
The text was updated successfully, but these errors were encountered: