Hey all Anybody else having troubles with the `server` I ve

Question

Hey all Anybody else having troubles with the `server` I ve been getting a long traceback while running the server locally It seems that a `flow run` is stuck cached somewhere and some process is still firing a log I think this happened after I cancelled and deleted a few flows and flow runs I already uninstalled the server and installed it again but no success

Dan Moore · Answer

```ValueError Foreign key violation ``` I m no expert here but it sounds like there might be some mismatch between the server and the database

Dan Moore · Answer

are you persisting data or using an external db If possible maybe clear this data to see if that helps

wiretrack · Answer

I m using the server from docker and i `force rebuild` the containers and rebuilt my `venv`

wiretrack · Answer

that s probably the case but i wondering what might have happened to get the application into this state and why it still gives me error in a continuum fashion even after rebuilding the container and reinstalling the server

wiretrack · Answer

`DETAIL Key flow run id = d6004258 b75f 477b 9615 f4ddb9756c19 is not present in table flow run ` So from what I understand the `flow run` information persisted somewhere and this generates an inconsistency in the database i wonder if there s any way to clean the cache or something I can t see anything in the docs I even reconstructure the `~ prefect` folder but didn t work as well

wiretrack · Answer

Immediately after the server starts this is the error ```apollo 1 | PayloadTooLargeError request entity too large apollo 1 | at readStream apollo node modules raw body index js 155 17 apollo 1 | at getRawBody apollo node modules raw body index js 108 12 apollo 1 | at read apollo node modules body parser lib read js 77 3 apollo 1 | at jsonParser apollo node modules body parser lib types json js 135 5 apollo 1 | at Layer handle as handle request apollo node modules express lib router layer js 95 5 apollo 1 | at trim prefix apollo node modules express lib router index js 317 13 apollo 1 | at apollo node modules express lib router index js 284 7 apollo 1 | at Function process params apollo node modules express lib router index js 335 12 apollo 1 | at next apollo node modules express lib router index js 275 10 apollo 1 | at cors apollo node modules cors lib index js 188 7 postgres 1 | 2021 01 05 05 02 49 134 UTC 85 ERROR insert or update on table log violates foreign key constraint log flow run id fkey postgres 1 | 2021 01 05 05 02 49 134 UTC 85 DETAIL Key flow run id = d6004258 b75f 477b 9615 f4ddb9756c19 is not present in table flow run postgres 1 | 2021 01 05 05 02 49 134 UTC 85 STATEMENT WITH log mutation result alias AS INSERT INTO public log created tenant id is loaded from archive task run id name id updated message timestamp level flow run id info VALUES DEFAULT $1 uuid DEFAULT $2 uuid $3 text $4 uuid DEFAULT $5 text $6 timestamptz $7 text $8 uuid $9 jsonb RETURNING CASE WHEN true THEN NULL ELSE hdb catalog check violation insert check constraint failed END log all columns alias AS SELECT flow run id tenant id task run id timestamp name level message info id created updated is loaded from archive FROM log mutation result alias SELECT json build object affected rows SELECT COUNT FROM log all columns alias ```

Dan Moore · Answer

Are you hitting the server from your browser at this point Perhaps the browser has cached flows and is trying to load previous ones via their Id which no longer exist

wiretrack · Answer

no this was right after the start of the server I got the cache clean after cleaning mac s library cache and several restarts