[SOLVED] OTRS system inconsistencies

[amdc]

Hello Guys,

I need a bit of help here in understanding why does one of these two systems doesn't seem to follow configurations properly

I am trying to understand why the production server (1st OTRS system) doesn't seem to fetch emails sent to its relative postmaster account, now on system logs i saw something about "No Priority for 3 normal found!" and based on my research that this has something to do with the priority settings which I have changed, but of course I have to try everything out on my development server (2nd OTRS system) before implementing any changes, that's where I found out that the 2nd system doesn't seem to reflect changes made to its system configurations.. I went to (2nd sys) Core::Postmaster and checked that it's currently set to "3 normal" and priority settings currently has that "3 normal" in "valid" state, now for testing I tried turning its state to "invalid" and even changed the priority name to "44 test" but the mail sent is still successfully getting inside OTRS and more surprisingly it is reflecting the "44 test" in the created ticket which I have changed in the priority list but NOT in its Core::Postmaster

just to summarize

Mail sent to Postmaster account ---

1st system -- Cant process mail
priority name "3 normal" - changed to "xxxxxxx"
Core::Postmaster >PostmasterDefaultPriority> "3 normal"
sys log error : "No Priority for 3 normal found!"

2nd system -- mail successfully being created with "44 test" listed as its Priority on ticket information
priority name "3 normal" - changed to "44 test"
Core::Postmaster >PostmasterDefaultPriority> "3 normal"

both of them are on OTRS version 3.0.11

Thanks,
amdc

[amdc]

after further tests it came evident that it was just being delayed.

resolved.