Extension Not Posting? A Pre-Support Troubleshooting Checklist

The message to support that wastes the most time is "the extension is not posting." It can mean the icon is missing, the login failed, the queue is empty, the daily limit is doing its job, Facebook showed a checkpoint, or a vehicle is sitting in posting while someone stares at a delay. Each of those has a different fix. Sending all of them to the same email as a single complaint slows the store down.

This pre-support troubleshooting checklist is what a manager should run before anyone writes info@posttomarket.com. It is written for used-car managers, internet directors, and the admin who owns logins. It uses only real product behavior: a Chrome extension that signs in with email, posts one vehicle at a time to Facebook Marketplace (and can also post to the user's Facebook profile and groups), human-like delays, and server-enforced daily limits. PostToMarket is independent and is not affiliated with, endorsed by, or sponsored by Meta. No checklist can guarantee Facebook will accept a listing.

Start With the Kind of Extension Not Posting

Name the symptom before you touch settings. "Not posting" is four different problems.

Four symptoms, four paths

1. The extension is not available in Chrome. Install and sign-in problem. Not a queue problem.
2. The extension is signed in, but nothing starts. Queue, status, or daily-limit problem.
3. A unit starts and never finishes. In-flight posting or a Facebook stall. See stuck-posting and failed-post articles after this checklist.
4. Units complete in PostToMarket but you cannot find them on Marketplace. Distribution or account-side visibility, which is not the same as the extension refusing to run.

If you skip this split, you will "fix" the extension while the real issue is an empty associate queue.

Pre-Support Troubleshooting Checklist: Browser and Sign-In

Work from the outside of the machine inward.

Chrome and install

• Confirm the person is in Chrome, not in a random browser where the extension was never installed.
• Confirm the extension is installed and visible. If it disappeared after a Chrome update, install it again rather than assuming the product is down.
• Confirm they are not in a guest profile or a separate Chrome user that does not have the extension.

A full clean install sequence lives in PostToMarket Chrome Extension Setup Guide for Dealership Teams. Use that when the machine is new or was just re-imaged. This checklist is for a machine that used to work.

Email sign-in, not a shared password

The extension signs in with email. There are no API keys to paste, which means the failure mode is almost always the wrong person signed in, or nobody signed in:

• The email matches that user's PostToMarket login.
• They did not sign into a colleague's session "just for today."
• A departed employee is not still the signed-in identity on a shared desktop.

Shared logins are a security problem and a diagnostic problem. You cannot tell whose daily limit applied if three people used one email. Signing Into the PostToMarket Extension With Email covers rollout and offboarding. Offboard first if the signed-in user should not have access.

Facebook session in the same browser

The extension posts as the Facebook user who is logged into that Chrome profile. Check:

• The intended Facebook account is logged in.
• There is no checkpoint, login review, or "confirm it's you" loop sitting in another tab.
• They did not switch Facebook accounts after signing into the extension.
• Multiple Chrome profiles are not mixed (work profile vs. personal profile).

If Facebook is asking the person to verify identity, that is not an extension defect. Complete Facebook's flow or stop posting until the account is usable. Check current Meta policies rather than guessing.

Pre-Support Troubleshooting Checklist: Queue, Status, and Pace

If sign-in looks clean, the product may be doing exactly what you configured.

Confirm there is something to post

• The user's Queue actually contains vehicles.
• Associates were assigned work. They cannot add from inventory. An associate with an empty queue will report "it's not posting."
• Sales reps who self-queue did not forget to add units today.
• The team queue view does not show the units claimed by someone who already left.

Empty queue is the most common "extension broken" ticket on a Monday.

Confirm the vehicles are in a postable status

• Draft units need to be queued before they will post.
• Posted units should not be posted again as a refresh trick.
• Sold units should be archived, not forced through the extension.
• Failed units need triage, not a blind start of the whole list.
• Posting means something is already in flight. Starting another vehicle on a second machine fights one-at-a-time posting.

Confirm you are not waiting on a delay or a daily limit

Human-like delays are supposed to feel slower than a click-storm. Server-enforced daily post limits will stop additional posts when the day is done, even if the queue still has cars. That is a design choice so pacing does not depend on memory.

If the complaint is "it stopped at 3 p.m. with units left," check whether the account already posted a full day by conservative standards. Do not work around the limit by posting manually in another tab. That workaround is one of the operational mistakes that commonly cause problems.

Train new associates that a pause between vehicles is normal. If they close Chrome during the pause, they create stuck posting states.

Facebook-Side Stops That Look Like Extension Failure

Before you email support, look at the page the extension is driving.

Notices, checkpoints, and listing rejections

If Facebook displayed a reason, follow that reason. Check current Marketplace and commerce rules. Do not ask support to override a Meta notice. Do not create a second profile to dodge it. Capture what appeared (in your own words) so a later ticket is specific.

Duplicate and availability issues

Trying to post a VIN that is already live, or a unit that sold an hour ago, will look like "it won't post" from the floor's point of view. Mark sold and archive. Do not relist to unstick a feeling.

Profile and groups vs. Marketplace

The extension can post to Marketplace and also to the user's Facebook profile and groups. If the team expected a Marketplace listing and someone was posting only to a group, the vehicle is "not on Marketplace" without the extension being dead. Align the destination with the manager's rule for that day. Pace still applies; do not spray groups as a catch-up tactic.

What to Send Support If the Checklist Still Fails

When the machine, sign-in, Facebook session, queue, status, and pacing checks all look clean, write a useful note to info@posttomarket.com. Getting Help: How to Contact PostToMarket Support is the longer template. The short version:

• Email login used in the extension.
• Chrome profile (work vs. personal) and whether the extension was reinstalled.
• VIN or stock number of the unit that would not post.
• Inventory status shown (draft, posting, posted, sold, failed).
• Whether a Facebook notice appeared.
• Approximate time, and whether other units posted earlier the same day from that login.
• What you already ruled out from this checklist.

Do not send passwords. Do not send a video of a blank desktop with no VIN. Do not copy ten people. One manager-owned ticket with facts is enough.

A manager's five-minute version

If you only have five minutes on the floor:

1. Right person signed into the extension?
2. Right Facebook account in that Chrome?
3. Anything in their queue?
4. Are they in the middle of a delay or at a daily limit?
5. Any notice on screen?

If the answers are yes, yes, yes, no, no, then gather the VIN and email support. If any answer is wrong, fix that first.

How PostToMarket Automates This

When the extension is not posting, the cause is usually operational: wrong login, empty associate queue, in-flight status, or a limit doing its job. PostToMarket gives you the surfaces to check those causes without inventing a parallel tracker. It cannot make Facebook accept a listing, and it cannot finish a post on a machine that is asleep.

• Email sign-in (no API keys) is the identity you verify first.
• Personal queues, manager assignment, and rep self-queue explain empty vs. loaded work.
• Inventory statuses tell you whether the unit is even eligible.
• One vehicle at a time and human-like delays explain pauses that get reported as freezes.
• Server-enforced daily limits explain a hard stop that is not a crash.
• Team queue view shows claims sitting with the wrong person.
• Import history matters when "nothing posts" because the day's file never produced clean drafts.

The checklist is short because those facts already live in the product.

Run the Checklist Before You Write the Email

Support is faster when the store has already eliminated empty queues, signed-out sessions, and Facebook notices. If the extension is not posting, run this pre-support troubleshooting checklist first. Messaging the owner the moment an associate shrugs is how you pay in delay for problems a manager can see in five minutes.

PostToMarket includes the extension, queues, statuses, and paced posting on both plans. A floor that needs several people signed in should use the Dealership plan at $299 per month with up to 13 logins so you can actually tell whose session failed. A one-person lot can stay on Starter at $59 per month with a single login and the same extension.

Start your 10-day free trial via secure Stripe checkout. Install Chrome, sign in with email, queue one clean unit, and learn what "posting" looks like when it is working — so the next incident is a checklist, not a guess. Cancel anytime.