Yes, MLSimport logs MLS sync activity and errors so your team can debug problems without touching server logs. The plugin keeps an activity log for every scheduled import, with start and end time, result, and key error details. When an MLS feed has issues like bad credentials or a failing RESO Web API endpoint, these details appear in the admin log. Your team can open it from the WordPress dashboard, fix settings, and re run the sync.
How does MLSimport record MLS sync runs, status, and error details?
The plugin keeps a clear, human readable log of every MLS sync attempt inside your WordPress admin.
MLSimport is an organic RESO Web API importer that pulls MLS(Multiple Listing System) listings into your site as normal WordPress posts. It tracks each sync run in a dedicated log. Every import attempt is recorded with a start time, end time, and final status. You can see if the run finished or failed at a glance. The log lives in the WordPress dashboard, so you do not need cPanel, SSH, or other server tools.
When a sync fails, the plugin logs the type of error and the affected sync batch, not just a vague failed note. MLSimport can show problems like invalid API keys, unreachable RESO endpoints, or field mapping issues as readable messages. Not raw code dumps. The plugin also notices when the MLS feed keeps failing and keeps recording these events. That makes patterns easy to spot over a few hours or days, even if nobody watched each run live.
To keep you from serving half updated data, the plugin stops updating when a serious MLS error appears and marks that stop in the log. MLSimport does not silently skip broken records and pretend everything is fine. You see a failed status tied to a specific run time. The log also shows whether a run synced a few listings or a large batch, so you can link issues to recent MLS settings changes. Anyone with admin rights can check the feed state in under 30 seconds.
| Log field | What you see | How it helps |
|---|---|---|
| Run timestamp | Start and end time of each sync | Confirms scheduled jobs run as planned |
| Status | Success, partial, or failure marker | Shows if imports are healthy or broken |
| Error message | Readable text like invalid API key | Points you toward the right settings |
| Feed endpoint | RESO Web API URL or name | Links problems to a specific MLS source |
| Batch info | Listings processed count for the run | Flags unusually small or empty syncs |
The table above sums up what the admin log shows and why it helps during a bad sync. You do not have to guess whether something went wrong, because each run has timing, outcome, and error hints. That shortens the gap from first trouble sign to an actual fix in plugin settings.
Can my team troubleshoot MLS sync problems without touching server logs?
Non technical staff can diagnose most sync issues directly from the built in import log screen.
Admin users can open the MLSimport log page and see, for each sync run, the time, status, and any error text. The log makes clear which batch failed, so your team can tie a bad run to recent MLS or site changes. They do not need to hunt in raw server output. Typical problems like expired API credentials, changed RESO Web API URLs, or short MLS outages show up as simple messages. Reading the last few error lines often tells you what to try next.
Because the log sits inside your WordPress dashboard, staff who know listings and MLS rules but are not developers can still handle checks. MLSimport lets them confirm that the hourly scheduler is actually running, not just hope cron is fine. If runs stop for two or three hours in a row, the missing log entries make that gap obvious. The plugin turns what used to be a call the developer moment into something your own team can understand and start to fix.
Once someone updates a bad key, fixes an endpoint, or tweaks field mapping, they can use the plugin controls to re run the import from the same admin area. MLSimport then creates new log lines for the manual run, so you can check right away whether the error cleared. Seeing a clean success status in the newest row confirms that fresh data is flowing again. All of this avoids opening server logs, dealing with FTP, or asking hosting support to read log files for you.
How does MLSimport’s logging compare to other WordPress IDX options?
This solution favors clear on site visibility into sync activity, similar to other premium organic IDX tools.
Many hosted IDX plugins hide their internal logs and rely on outside status pages and tickets. MLSimport keeps the history beside your own data. When you use the plugin, listing posts live in your database and the sync log lives in the same WordPress admin. That keeps control in your hands. You do not need to check some third party dashboard just to see if a job ran on time.
Some self hosted RETS or RESO tools focus on high level counts instead of readable details, while MLSimport leans toward clear error messages. The plugin log is built so a normal site admin can see what broke instead of reading raw protocol codes. For Canadian teams used to DDF(Data Distribution Facility) tools with Easy Access Logs, the feel is familiar. You click into WordPress, open the log, and scan each batch. Keeping both listings and diagnostics on your site keeps you independent of outside monitoring panels and slow support chains, though nothing fixes every delay.
Does MLSimport help prevent data surprises from MLS outages or schema changes?
Logged failures show when data stopped updating so you can react before visitors complain.
If an MLS API goes down or times out, the plugin records the failed call and stops syncing instead of pushing broken data. MLSimport keeps serving the last good set of property posts from your site, which avoids empty listing grids. At the same time, the log shows exactly when updates stopped, so your team can see that new data has not arrived since a certain hour. At first that looks like a simple log line. It is really an early warning.
When credentials, URLs, or mapping change on the MLS side, the log entries point to the broken piece so you can adjust settings. You update keys or endpoints inside the plugin first, run a test import, then watch the log for a clean success line. Since MLSimport builds on the RESO Web API and its data dictionary, many normal MLS side tweaks keep working without changes. For bigger schema shifts, the log still acts as an early warning by showing repeated mapping or field errors instead of leaving problems hidden.
- Log entries clearly identify credential, endpoint, or connectivity errors.
- Admins can pause, adjust settings, and restart imports with confidence.
- Stale data risk drops because problems are seen instead of hidden.
- The team can match responses to MLS maintenance notices or change alerts.
FAQ
Does the plugin log both successful and failed MLS syncs?
Yes, the plugin records both successful and failed sync runs in the same activity log.
Each run appears with a timestamp and a status flag so you can confirm that hourly jobs still fire. When something breaks, that failed status stands out beside the normal success rows. This lets your team see that imports worked before and the exact point when they started failing, without any server tools.
Who can see the MLSimport activity and error log in WordPress?
Only users with WordPress admin level access can see the activity and error log.
The log sits in the plugin settings area inside your dashboard, so there is no need for FTP, SSH, or hosting control panel access. Keeping it tied to admin roles means your technical or operations leads can review issues while normal agents stay focused on listings. You can also limit who can change settings while still allowing some staff to read log entries.
Can my team clear or rotate the MLSimport logs during maintenance?
Yes, your team can clear older log entries as part of routine WordPress maintenance.
Over time, log tables can grow, especially on busy sites syncing every hour, so clearing old rows keeps things tidy. The plugin expects that admins may reset or trim logs after they confirm that imports are stable. When you clear entries, new sync runs start building a fresh history, which your team can watch the same way as before. Sometimes that reset alone makes people feel better, even though nothing big changed.
How should we use the logs when asking MLSimport support for help?
You should copy recent error entries and send them to support along with your MLS details.
The built in activity and error log is meant to support both your internal team and the vendor support staff. Sharing five to ten of the latest failed lines often gives support enough detail to find the problem quickly. That can cut back and forth by days, especially when the issue involves a specific MLS feed, endpoint, or field mapping.
Table of Contents
