Excel task in Sol 5.6 reportedly triggered an account warning
In a case, Sol 5.6 was asked once to build a complex Excel workbook for tracking the finances of a rental property. Sol ran a large amount of code to create the file, and some of that code failed. One error indicated that the source could not be retrieved because the code may have been .
The task was sent for a , but the completed workbook arrived correctly after about ten minutes. Later that day, an email said the account had been flagged for a “” and could be banned if violations continued. A detailed appeal took about 30 minutes to prepare and was rejected within two hours.
The quick rejection raised suspicion that the appeal was judged automatically, possibly by the same kind of system that raised the warning, but no evidence confirmed this.
Key points
- The request was to create an Excel workbook for rental-property finances.
- Sol 5.6 ran code, encountered errors, and sent the task for a .
- The requested workbook was successfully produced after about ten minutes.
- An account warning arrived later, and an appeal that took 30 minutes to write was rejected within two hours.
- The claim that an system rejected the appeal is an , not a confirmed fact.