Error codes

Every error message in Ploffo shows a code, for example PLF-SYS-0002. Look it up below: what happened, and whether you solve it yourself or send us the code.

System — PLF-SYS

Code	What happened	Who fixes it
PLF-SYS-0001	A server setting is missing ({naam}). This is on us, not on you.	This is on us. Send us the code if it keeps happening.
PLF-SYS-0002	Something went wrong on our side. Try again; if it keeps happening, send us this code.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-SYS-0003	This request is not valid. Reload the page and try again.	You can solve this yourself.

Database — PLF-DB

Code	What happened	Who fixes it
PLF-DB-0001	This record is final and cannot be changed or deleted.	This is on us. Send us the code if it keeps happening.
PLF-DB-0002	A timing agreement is never edited; you record a new one.	This is on us. Send us the code if it keeps happening.
PLF-DB-0003	An agent draft is never edited; an edited reply is stored separately.	This is on us. Send us the code if it keeps happening.
PLF-DB-0010	This does not belong to your space.	You can solve this yourself.

Signing in and access — PLF-AUTH

Code	What happened	Who fixes it
PLF-AUTH-0001	You are not signed in. Sign in and try again.	You can solve this yourself.
PLF-AUTH-0002	You do not have access to this space. Ask the owner for an invitation.	You can solve this yourself.
PLF-AUTH-0003	Your role ({rol}) does not allow this. You need at least {nodig}.	You can solve this yourself.

Members and invitations — PLF-WS

Code	What happened	Who fixes it
PLF-WS-0001	This invitation has expired. Ask whoever invited you for a new one.	You can solve this yourself.
PLF-WS-0002	This invitation has already been used.	You can solve this yourself.
PLF-WS-0003	There must always be one owner left. Make someone else an owner first.	You can solve this yourself.
PLF-WS-0004	This invitation is for {verwacht}, but you are signed in as {aangemeld}. Sign in with the right address.	You can solve this yourself.
PLF-WS-0005	That is not a valid email address.	You can solve this yourself.
PLF-WS-0006	This space will be permanently deleted on {datum}. Until then you can only export or undo the deletion.	You can solve this yourself.
PLF-WS-0007	Only the owner can delete this.	You can solve this yourself.
PLF-WS-0008	Your account will be permanently deleted on {datum}. Undo the deletion to continue.	You can solve this yourself.

Time — PLF-TIME

Code	What happened	Who fixes it
PLF-TIME-0001	We do not know the time zone “{zone}”. Pick one from the list.	You can solve this yourself.
PLF-TIME-0002	{uur} does not exist on {dag}: the clock jumps forward that night. Pick a time after {eersteGeldige}.	You can solve this yourself.
PLF-TIME-0003	That is not a valid date or time.	You can solve this yourself.

Scheduling — PLF-PLAN

Code	What happened	Who fixes it
PLF-PLAN-0001	That time has already passed. Pick a moment in the future.	You can solve this yourself.
PLF-PLAN-0002	There is already a post on {kanaal} at {anderUur}. We keep {uren} hours between two posts on the same channel. Pick another time, or say why it has to go anyway.	You can solve this yourself.
PLF-PLAN-0003	This post has already gone out and can no longer be cancelled.	You can solve this yourself.
PLF-PLAN-0004	Ploffo could not pick a time on {dag}: {waarom} Pick a time yourself.	You can solve this yourself.
PLF-PLAN-0005	{kanaal} needs to be reconnected before you can schedule to it. Go to Channels.	You can solve this yourself.
PLF-PLAN-0006	Pick at least one channel.	You can solve this yourself.
PLF-PLAN-0007	This post is {status} and can no longer be scheduled.	You can solve this yourself.
PLF-PLAN-0008	This suggestion is no longer valid: the schedule has changed in the meantime.	You can solve this yourself.
PLF-PLAN-0009	This is not (or no longer) a proposal. There is nothing to approve or move.	You can solve this yourself.

Posts — PLF-POST

Code	What happened	Who fixes it
PLF-POST-0001	This post has already gone out and is kept as proof. It can no longer be deleted.	You can solve this yourself.
PLF-POST-0002	This post is {status} and can no longer be changed.	You can solve this yourself.
PLF-POST-0003	We cannot find this post (any more).	You can solve this yourself.

Folders and the planning round — PLF-MAP

Code	What happened	Who fixes it
PLF-MAP-0001	This image is already used or already waiting. An image never goes into the calendar twice.	You can solve this yourself.
PLF-MAP-0002	The drop folder is empty. Drag your finished images in first.	You can solve this yourself.
PLF-MAP-0003	The rhythm is missing or wrong: between {min} and {max} posts per week, and at least one day on which to post.	You can solve this yourself.
PLF-MAP-0004	No connected channel can take this file ({bestand}).	You can solve this yourself.
PLF-MAP-0005	There is no image named {naam} in the drop folder. Drag the image first, then the text.	You can solve this yourself.
PLF-MAP-0006	The window is wrong: the last day is before the first.	You can solve this yourself.
PLF-MAP-0007	This item is not (or no longer) in the folder.	You can solve this yourself.
PLF-MAP-0008	This file is not in the build folder or is already part of a post in the making.	You can solve this yourself.

Media — PLF-MEDIA

Code	What happened	Who fixes it
PLF-MEDIA-0001	This file is {grootte}. The maximum is {max}.	You can solve this yourself.
PLF-MEDIA-0002	We cannot use a file of type {type}. Accepted: {toegelaten}.	You can solve this yourself.
PLF-MEDIA-0003	Saving your file failed after {pogingen} attempts. Try again in a moment.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-MEDIA-0004	This file is not a readable image. Export it again as JPEG or PNG.	You can solve this yourself.

Bluesky — PLF-BS

Code	What happened	Who fixes it
PLF-BS-0001	Bluesky rejects this sign-in. Check your handle (e.g. name.bsky.social) and create a new app password.	You can solve this yourself.
PLF-BS-0002	This text has {aantal} characters; Bluesky allows {max}. Shorten it by {teveel} characters.	You can solve this yourself.
PLF-BS-0003	This post has {aantal} images; Bluesky allows {max} per post.	You can solve this yourself.
PLF-BS-0004	One image is still larger than Bluesky allows ({max}) after compression. Supply a smaller one.	You can solve this yourself.
PLF-BS-0005	Bluesky does not display files of type {type}. Use JPEG, PNG, WebP or GIF.	You can solve this yourself.
PLF-BS-0006	Bluesky no longer accepts our access to {kanaal} (app password revoked or changed). Reconnect the channel; your scheduled posts stay in place.	You can solve this yourself.
PLF-BS-0007	Bluesky asks us to wait (too many requests). We will retry automatically.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-BS-0008	Bluesky cannot be reached right now. We will retry automatically.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-BS-0009	Bluesky rejects this post. Their message: “{melding}”	You can solve this yourself.
PLF-BS-0010	A post with no text and no image cannot go out. Write something or add an image.	You can solve this yourself.
PLF-BS-0011	Bluesky has suspended or deactivated this account. Sort that out with Bluesky, then reconnect here.	You can solve this yourself.
PLF-BS-0012	Sending an image to Bluesky failed after {pogingen} attempts. We will retry later.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-BS-0013	This looks like your regular password. Give Ploffo an app password (shaped xxxx-xxxx-xxxx-xxxx): you can revoke it without touching your account.	You can solve this yourself.
PLF-BS-0014	We cannot find the handle “{handle}” on Bluesky. Check that it is complete, e.g. name.bsky.social.	You can solve this yourself.
PLF-BS-0015	This Bluesky account is already connected here.	You can solve this yourself.

Publishing — PLF-PUB

Code	What happened	Who fixes it
PLF-PUB-0001	Publishing to {platform} is not possible yet. This channel arrives once the platform approves our application.	This is on us. Send us the code if it keeps happening.
PLF-PUB-0002	The access to this channel could not be read. Reconnect the channel.	This is on us. Send us the code if it keeps happening.
PLF-PUB-0003	An image of this post no longer exists in the media library. Add it again.	You can solve this yourself.

Deletion and export — PLF-EXPORT

Code	What happened	Who fixes it
PLF-EXPORT-0001	This export no longer exists. Request a new one under Settings › Your data.	You can solve this yourself.
PLF-EXPORT-0002	The export could not be built. We will retry and e-mail you the link.	Trying again helps. For a publish, Ploffo does that by itself.

Approval — PLF-GK

Code	What happened	Who fixes it
PLF-GK-0001	This approval link does not exist or has expired. Ask the sender for a new one.	You can solve this yourself.
PLF-GK-0002	The post “{titel}” has no day and hour yet. Schedule it first; then it can go in the dossier.	You can solve this yourself.
PLF-GK-0003	Pick at least one post for the dossier.	You can solve this yourself.
PLF-GK-0004	This dossier has already been decided or replaced by a newer version. Changes go into a new version.	You can solve this yourself.
PLF-GK-0005	Fill in your name and e-mail address: that is how the agency knows who agreed.	You can solve this yourself.
PLF-GK-0006	The post “{titel}” is already in an open dossier ({ronde}). Wait for that decision or make a new version of it.	You can solve this yourself.
PLF-GK-0007	The PDF dossier could not be created. We will retry; the approval link works in the meantime.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-GK-0008	This approver does not exist (any more) in this space.	You can solve this yourself.
PLF-GK-0009	This dossier is waiting for the client. Edit a post in it after their decision, or in a new version.	You can solve this yourself.
PLF-GK-0010	Sign-off is done by a person. Ploffo proposes; whoever stands behind this post gives the sign-off.	You can solve this yourself.
PLF-GK-0011	The post “{titel}” has not been signed off yet. Check it and sign it off; then it can go out.	You can solve this yourself.
PLF-GK-0012	This dossier is with your client. They decide; you can withdraw it or create a new version.	You can solve this yourself.

The API and MCP — PLF-API

Code	What happened	Who fixes it
PLF-API-0001	The API key is missing. Send it as Authorization: Bearer .	You can solve this yourself.
PLF-API-0002	This API key is unknown or revoked. Create a new one under Settings › API.	You can solve this yourself.
PLF-API-0003	An API key can only be created after payment. Choose a plan under Settings › Billing.	You can solve this yourself.
PLF-API-0004	A request with the same Idempotency-Key is still running. Wait for its answer instead of sending again.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-API-0005	Too many requests with this key. Try again in {seconden} seconds; see the X-RateLimit headers.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-API-0006	The field “{veld}” is missing or has the wrong shape. {verwacht}	You can solve this yourself.
PLF-API-0007	The same Idempotency-Key was already used for a different address ({pad}). Use a new key per request.	You can solve this yourself.
PLF-API-0404	This address does not exist in the API. The list is on docs.ploffo.com/api.	You can solve this yourself.

Subscription — PLF-ABO

Code	What happened	Who fixes it
PLF-ABO-0001	Only the account owner can change the plan or cancel.	You can solve this yourself.
PLF-ABO-0002	That does not fit in {plan}: {watWeg}. Close that first, or pick a bigger plan.	You can solve this yourself.
PLF-ABO-0003	Your plan allows {grens} workspaces. Add one or pick a bigger plan under Settings › Billing.	You can solve this yourself.
PLF-ABO-0004	Your plan allows {grens} channels across all your brands. Add one or pick a bigger plan under Settings › Billing.	You can solve this yourself.
PLF-ABO-0005	Your plan allows {grens} users across all your brands. Pick a bigger plan under Settings › Billing.	You can solve this yourself.
PLF-ABO-0006	Your trial has ended. Choose a plan under Settings › Billing; until then nothing goes out.	You can solve this yourself.
PLF-ABO-0007	This is already your plan.	You can solve this yourself.
PLF-ABO-0008	Sending a dossier to your client is not part of {plan}. You sign off on your posts here yourself; to let someone else approve, pick a bigger plan under Settings › Billing.	You can solve this yourself.

Creating images — PLF-BEELD

Code	What happened	Who fixes it
PLF-BEELD-0001	That should be a real photo. Drop it in your build folder, or put it in the brand folder if it comes back often. An image without it I will gladly make.	You can solve this yourself.
PLF-BEELD-0002	The image could not be created. We will retry automatically; no credit is deducted.	Trying again helps. For a publish, Ploffo does that by itself.
PLF-BEELD-0003	Your image credit for this month is used up. You can still make a draft; keeping a render waits for next month or a bigger plan.	You can solve this yourself.
PLF-BEELD-0004	I do not know what {wat} looks like. Put a photo of it in the brand folder and I will use it every time.	You can solve this yourself.

Help inside the app — PLF-HULP

Code	What happened	Who fixes it
PLF-HULP-0001	This conversation does not exist or is not yours.	You can solve this yourself.
PLF-HULP-0002	That screenshot is too large (up to {mb} MB).	You can solve this yourself.