The daily sync only retrieves changes from PERSCOM, any changes you make inside of your forumify website should be sent to PERSCOM near-instant, just seconds after the change is made. You can check the logs for this in forumify Admin Panel -> PERSCOM -> Sync. For this sync (both sending and retrieving from PERSCOM) the async and scheduler message queue workers need to be running (you can "docker exec -it <container_name> bash" followed by "supervisorctl status" to see if they are running).
Profile images are never synced, we (ab)use PERSCOM.io's profile avatar and banner to store the plugin's signature and uniform images.
Award images should be sent to PERSCOM seconds after you upload it. If this fails, you can see and retry failed messages (run these commands in the docker exec shell), or the messenger_messages table to see why it failed. If the async worker isn't running, the messenger_messages table will also just fill up but all messages will be stuck in status "default" or "async".
We'd also like to reiterate that the PERSCOM.io plugin for forumify is a legacy plugin, and while it will continue to receive support for the foreseeable future, we recommend all users of the plugin that do not need PERSCOM.io to switch to MILHQ. It's cheaper overall, no dual system sync complexities, more milsim oriented features, and it offers a 1-click seamless migration for users of the PERSCOM plugin.
We checked the Forumify sync logs, and the sync is in fact running and completing successfully. However, the issue appears to be deeper than the scheduler itself.
From the logs, we can see that the sync completes, but during the AwardRecord stage we receive repeated messages such as:
AwardRecord: Skipping item with perscom id XX: No award found for award record.
This suggests that Forumify is retrieving award records from PERSCOM, but is unable to resolve them against the corresponding award entries locally.
Just to clarify our setup:
All changes are made directly in PERSCOM, not within Forumify. We are not pushing any data from Forumify to PERSCOM.
Our issue is specifically with the PERSCOM → Forumify synchronization. The daily sync does not appear to be pulling any updates:
Award images updated in PERSCOM are not reflected in Forumify
Other changes also remain outdated
To add context, we have other systems connected directly to the PERSCOM API, and those are receiving the correct and up-to-date information, including images and profile data.
That's not the workflow we suggest, the intended usage is to always edit and manage within forumify, and let it push to PERSCOM.io. If you do not follow this path, then expect things to break. forumify keeps track of changes made to entities, if it fails to push them to PERSCOM.io for whatever reason, then the entity is marked as "dirty" and will never receive updates during syncs again until it does manage to sync (probably because of a stuck message in messenger_messages).
So the normal flow is:
User makes edit in forumify
forumify marks resource "dirty", and schedules an update to perscom.io in the background (through messenger_messages)
message queue worker processes the changes, updates them in perscom, and unmarks the entity as dirty
nightly sync updates all non-dirty resources
What is likely happening for you:
Some entities were edited in forumify
resource was marked dirty
message queue worker failed to process changes (PERSCOM API outage, validation error, ....)
resource was kept as dirty
nightly sync ignores any updates from perscom.io to avoid overwriting pending changes
The error you see about award not found means that someone has an award record, for which you have deleted the underlying award in PERSCOM.io. For forumify, all award records must have a linked award. Same with ranks and qualifications.
To manually unblock it, you can go into the relevant perscom_.. tables and set the "dirty" column to 0, some entities, such as those with images and users, will also have separate columns for image_dirty, uniform_dirty,... those would also have to be set to 0 for them to receive updates again.
We will not be changing this behavior, as most of our communities use this workflow as the default and the plugin was always intended to be a complete wrapper for PERSCOM.io, and you are using the plugin in a scenario for which it was never tested or validated. If you want to make it possible to change this, and make PERSCOM.io the leading factor (essentially completely ignoring any changes from forumify), feel free to make a PR on our plugin to add a toggle or something that modifies the sync behavior.
Hi everyone,
I’m currently running into an issue with the Perscom integration via the Forumify plugin, specifically regarding the automatic synchronization.
According to the documentation, there should be a daily automatic sync, but this does not appear to be functioning correctly on our end.
Issues observed:
Any guidance on how to troubleshoot or resolve this would be greatly appreciated.
Thanks in advance!
Hi Hughes,
The daily sync only retrieves changes from PERSCOM, any changes you make inside of your forumify website should be sent to PERSCOM near-instant, just seconds after the change is made. You can check the logs for this in forumify Admin Panel -> PERSCOM -> Sync. For this sync (both sending and retrieving from PERSCOM) the async and scheduler message queue workers need to be running (you can "docker exec -it <container_name> bash" followed by "supervisorctl status" to see if they are running).
We'd also like to reiterate that the PERSCOM.io plugin for forumify is a legacy plugin, and while it will continue to receive support for the foreseeable future, we recommend all users of the plugin that do not need PERSCOM.io to switch to MILHQ. It's cheaper overall, no dual system sync complexities, more milsim oriented features, and it offers a 1-click seamless migration for users of the PERSCOM plugin.
Hi,
Thanks for the clarification.
We checked the Forumify sync logs, and the sync is in fact running and completing successfully. However, the issue appears to be deeper than the scheduler itself.
From the logs, we can see that the sync completes, but during the AwardRecord stage we receive repeated messages such as:
This suggests that Forumify is retrieving award records from PERSCOM, but is unable to resolve them against the corresponding award entries locally.
Just to clarify our setup:
All changes are made directly in PERSCOM, not within Forumify. We are not pushing any data from Forumify to PERSCOM.
Our issue is specifically with the PERSCOM → Forumify synchronization. The daily sync does not appear to be pulling any updates:
To add context, we have other systems connected directly to the PERSCOM API, and those are receiving the correct and up-to-date information, including images and profile data.
Appreciate your help.
Hello Hughes,
That's not the workflow we suggest, the intended usage is to always edit and manage within forumify, and let it push to PERSCOM.io. If you do not follow this path, then expect things to break. forumify keeps track of changes made to entities, if it fails to push them to PERSCOM.io for whatever reason, then the entity is marked as "dirty" and will never receive updates during syncs again until it does manage to sync (probably because of a stuck message in messenger_messages).
So the normal flow is:
What is likely happening for you:
The error you see about award not found means that someone has an award record, for which you have deleted the underlying award in PERSCOM.io. For forumify, all award records must have a linked award. Same with ranks and qualifications.
To manually unblock it, you can go into the relevant perscom_.. tables and set the "dirty" column to 0, some entities, such as those with images and users, will also have separate columns for image_dirty, uniform_dirty,... those would also have to be set to 0 for them to receive updates again.
We will not be changing this behavior, as most of our communities use this workflow as the default and the plugin was always intended to be a complete wrapper for PERSCOM.io, and you are using the plugin in a scenario for which it was never tested or validated. If you want to make it possible to change this, and make PERSCOM.io the leading factor (essentially completely ignoring any changes from forumify), feel free to make a PR on our plugin to add a toggle or something that modifies the sync behavior.