This page lists every status portierX shows for its connections to other systems: on the connection's own page, on each run in a Sync Log, on each version of an imported master key plan, and on each run of the HR file. The connections are under Integrations, on the Connected tab.
Also called: status, state, badge, sync status, import status.
Every connection's page shows a status beside the connection's name. A tile under Integrations shows its category, not a status.
Status | Meaning | What to do |
|---|---|---|
Active | The connection serves data. This holds for an access control system that passed its check on Activate, a master key plan with an applied version, single sign-on with a verified domain, provisioning from Entra ID and the HR file. A master key plan stays Active while a further file is processed or after one has failed. | Nothing. |
Review Required | A master key plan version or an HR file run waits for your decision. | Open the version from Import Log, or the run from the notice on the HR file's page. |
Inactive | The connection serves nothing: a draft, a master key plan whose first version is not applied, or single sign-on without a verified domain. | Finish the set-up. A draft carries the notice Draft, not yet active. with Continue setup. |
Paused | The HR file does not read its folder. | Choose Resume imports on the HR file's page. |
SALTO, dormakaba MATRIX, ASSA ABLOY eCLIQ and Interflex IF-6040 show these values on the Summary tab.
Value | Meaning | What to do |
|---|---|---|
Connected under Sync Health | portierX reaches the system with the stored settings. It does not say whether the data is right. | Nothing. |
Error under Sync Health | The last check failed. Health check failed appears with Review Configuration. | Check the address, the protection layer and the credential. The causes are on A sync failed or brought nothing across. |
Health check is in progress under Sync Health | The check is running, when the page opens or after Test Connection. | Wait for the result. |
Active under Sync Status | The connection is active and syncs on its schedule. How each run ended is on Sync Log. | Nothing. |
Draft under Sync Status | The connection is registered, not activated, and does not sync. | Choose Continue setup, then Activate. |
OK beside Returned | The last connection test passed. Last test on gives its date. | Nothing. |
Failed beside Returned | The last connection test failed. | As for Error. |
Last Sync shows a date and time, or Never. The start of every run is under Started on Sync Log.
Each row of the Sync Log of SALTO, dormakaba MATRIX, ASSA ABLOY eCLIQ and Interflex IF-6040 is one run, reading or writing.
Status | Meaning | What to do |
|---|---|---|
Success | The run went through. | Nothing. |
Partial Success | Part of the run went through and part did not. The number of records that failed is under Failed. | Open the run and read Errors. |
Failed | The run did not complete. | Open the run and read Errors. The causes are on A sync failed or brought nothing across. |
Skipped | ASSA ABLOY eCLIQ and Interflex IF-6040 only: another run of the same connection was in progress, so this one did no work. | Nothing. The run in progress covers the same work. |
Beside the status, a line says whether portierX delivers the run again:
Line | Meaning |
|---|---|
Attempt 2 of 4, trying again | The run failed on a passing fault and is delivered again on its own. The first number is this delivery, the second the number under Attempts on Configuration. |
This run stopped after attempt 1 | The run is not delivered again, because another try would change nothing or the last attempt is used. The next scheduled run starts on its own. |
This run stopped | The same, for a run that carries no count of its own. |
Succeeded on attempt 2 of 4 | The run succeeded after a failed delivery. |
No line | The run succeeded at its first delivery, was skipped, or states nothing about a further delivery. |
The run's own page lists every record under What changed, with what happened to it:
Operation | Meaning |
|---|---|
Created | The record was created: in portierX by a read, or in the system by a write. |
Updated | Fields of the record changed. Each field is listed with its old and its changed value. |
Assigned | A key or card was assigned to a person. |
Revoked | A key or card was taken away from a person. |
Linked | A key or card was linked to a door. |
Pushed update | A change from portierX reached the system. |
Push pending | ASSA ABLOY eCLIQ took the change as a job. It reaches the key the next time the key is updated. |
Applied | The pending change is on the key. |
Removed in CLIQ Web Manager | The record no longer exists in the CLIQ Web Manager. It stays in portierX. |
Skipped | The run deliberately wrote nothing for this record. Reason says why. |
A record whose write failed carries Exception and the reason.
The Import Log of a connection that runs from an XML file lists each version with its status. The same status shows in the version's details.
Status | Meaning | What to do |
|---|---|---|
Processing | portierX reads and compares the file, or writes a version you applied. | Wait. While portierX reads the file, Discard Import in the row menu ends the version. |
Review Required | The version waits for your decision. The Summary shows This update requires your review. | Open Review Changes from the row menu. |
Completed | The version is applied. | Nothing. |
No changes | The file brought no change to the applied version. Nothing was written. | Nothing. |
Discarded | Someone discarded the version. Nothing from it was written. | Upload the file again with Update Version if you want it. |
Failed | The import did not complete. | View names the reason and the way on, for example Retry Import or Upload Different File. |
The applied version carries Current beside its number.
On Review Changes, and under What changed in a version's details, each row carries one of these statuses:
Status | Where | Meaning |
|---|---|---|
Updated | Items Requiring Review | The value differs between the applied version and the file. |
Will be added | Added & Removed Items | The item has come into the file. |
Will be removed | Added & Removed Items | The file no longer carries the item. |
Ignored | Skipped Items, or a row set to Keep Current or Ignore | The difference is not applied. |
Current | Unchanged | The item is the same in both. |
Added, Updated, Removed | What changed in the details | What the applied version did to the item. |
The HR file lists each finished run on its Sync Log. Its Summary shows the latest finished run with the same status, or No run yet.
Status | Meaning | What to do |
|---|---|---|
Success | The run applied and took every row. | Nothing. |
Partial Success | The run applied, and some rows were refused, each with its reason. The other rows applied. | Open the run and read Refused rows. |
No changes | The run applied, and the file matched what portierX holds. Nothing was written. | Nothing. |
Failed | The run could not complete, for example because the file was over 4 MB, dated before the last file applied, unreadable or missing a mapped column, or because it waited longer than 7 days for review. | Open the run with Open run. The reason is there. |
Discarded | An Organisation Admin discarded the run. Nothing from the file was written. | Nothing. |
A run that waits for an Organisation Admin sits above the finished runs with Waiting for review. The notice on the HR file's page names the reason. The reasons and the review are on Review, apply or undo an HR file run.
While it is reviewed, the run carries one of these statuses:
Status | Meaning |
|---|---|
Mapping to confirm | The run waits for the mapping of its columns to be confirmed. |
Comparing | portierX compares the file with the people. |
Review required | The preview is ready and waits to be applied or discarded. |
Applying | portierX writes the run. |
Applied | The run is written. |
Changes over the organisation's daily limit wait in the run under Held changes. Each carries its kind: Leaving date set, Leaving date moved, Leaving date cleared, Org unit change or Ended by Mirror. Each also shows one of these states:
State | Meaning |
|---|---|
Apply and Discard | The change waits for an Organisation Admin. |
"The last apply was refused" | The person's record did not take the change. It waits again. |
"The change was not written in time" | The write did not finish. The change waits again. |
Applying… | The change is being written. |
"Applied by" with a name and a time | The change is written. |
"Discarded by" with a name and a time | The change was discarded, with the reason typed, if any. |
"Replaced by the run of" with a time | A later run of the same source replaced the change. Nothing waits. |
Under Last checked, the HR file's Summary shows what the latest look at the folder found:
Line | Meaning |
|---|---|
The date and time alone | A file arrived and was imported. |
The date and time, then "Nothing arrived." | The folder was empty. |
The date and time, then "A file arrived and waits for review." | The file waits as a run for review. |
"Drop folder not set up. No file can arrive until it is." | No drop folder is set up for the source. |
"Could not read the folder. Trying again at the next check." | The look at the folder failed. The next check tries again. |
