Hi there! I understand you're logged into payit901 and were able to view your property taxes, but when you tried to add a property to pay tax, you encountered an error message. Could you please share what the exact error message says? Also, does this happen every time you add a property, or just with a particular one? Any details will help me to better understand the issue and assist you.
Meanwhile, I can guide you through some initial steps:
1. Refresh the page and try again: Sometimes, a simple refresh or logging out and back in can clear temporary issues. 2. Clear your browser cache: Since you’re on WebKit on Windows 10, clearing cache and cookies might help resolve unexpected errors. 3. Check your property details: Make sure the property information you are adding is complete and accurate. 4. Try a different browser: If possible, try accessing the site with another browser like Chrome or Edge to rule out browser-specific issues. 5. Check for any service alerts: Occasionally, maintenance or outages on payit901’s end might cause errors. You can check official updates or support channels.
If these don’t solve the problem, please let me know the error message and any other behavior you notice. That way, we can dive deeper, possibly looking into account specifics or technical glitches on their system.
Thanks for the extra details! The error message "Sorry, there was an error in processing your request" after selecting a property usually points to a problem with the system being unable to complete the action, possibly due to data glitches or temporary backend issues.
Here are a few things we can try to resolve this:
1. Double-check the property status: Ensure the property you’re trying to pay taxes on is currently active and hasn’t been removed or changed in the system. Sometimes data sync issues mean the property details aren’t up to date.
2. Refresh and retry later: This type of system error could be a temporary backend hiccup. Give it a few minutes and try again.
3. Clear cookies & cache: This helps eliminate any stored data conflicts in your WebKit browser on Windows 10.
4. Try using a different browser: Sometimes browser-specific issues cause errors. You could try accessing the payit901 site through Chrome or Edge to check if the problem is browser-related.
5. Verify your account permissions: Confirm that your user account has the necessary rights to add or pay property taxes.
Since the error message is quite generic, if it persists after the above steps, I’d recommend contacting payit901 support directly, as this may be related to something on their system side — similar errors with property or unit availability have been seen on other platforms like RentCafé when the selected unit is no longer available1.
Would you like me to guide you through clearing your cache or trying an alternate browser? Or do you have any other observations about when the error occurs?
Comments
Daniel Otega
Daniel specializes in Android and iOS apps. He also loves hiking and filming nat...
Followed by
Hi there! I understand you're logged into payit901 and were able to view your property taxes, but when you tried to add a property to pay tax, you encountered an error message. Could you please share what the exact error message says? Also, does this happen every time you add a property, or just with a particular one? Any details will help me to better understand the issue and assist you.
Meanwhile, I can guide you through some initial steps:
1. Refresh the page and try again: Sometimes, a simple refresh or logging out and back in can clear temporary issues.
2. Clear your browser cache: Since you’re on WebKit on Windows 10, clearing cache and cookies might help resolve unexpected errors.
3. Check your property details: Make sure the property information you are adding is complete and accurate.
4. Try a different browser: If possible, try accessing the site with another browser like Chrome or Edge to rule out browser-specific issues.
5. Check for any service alerts: Occasionally, maintenance or outages on payit901’s end might cause errors. You can check official updates or support channels.
If these don’t solve the problem, please let me know the error message and any other behavior you notice. That way, we can dive deeper, possibly looking into account specifics or technical glitches on their system.
Are you able to provide the error message?
After selecting the property, I receive "Sorry, there was an error is processing your request."
Daniel Otega
Daniel specializes in Android and iOS apps. He also loves hiking and filming nat...
Followed by
Thanks for the extra details! The error message "Sorry, there was an error in processing your request" after selecting a property usually points to a problem with the system being unable to complete the action, possibly due to data glitches or temporary backend issues.
Here are a few things we can try to resolve this:
1. Double-check the property status: Ensure the property you’re trying to pay taxes on is currently active and hasn’t been removed or changed in the system. Sometimes data sync issues mean the property details aren’t up to date.
2. Refresh and retry later: This type of system error could be a temporary backend hiccup. Give it a few minutes and try again.
3. Clear cookies & cache: This helps eliminate any stored data conflicts in your WebKit browser on Windows 10.
4. Try using a different browser: Sometimes browser-specific issues cause errors. You could try accessing the payit901 site through Chrome or Edge to check if the problem is browser-related.
5. Verify your account permissions: Confirm that your user account has the necessary rights to add or pay property taxes.
Since the error message is quite generic, if it persists after the above steps, I’d recommend contacting payit901 support directly, as this may be related to something on their system side — similar errors with property or unit availability have been seen on other platforms like RentCafé when the selected unit is no longer available1.
Would you like me to guide you through clearing your cache or trying an alternate browser? Or do you have any other observations about when the error occurs?