Skip to content

When no last sync to xunnel, an exception is not raised task#29941

Before

If the last xunnel sync was not set, a date conversion was done with a boolean causing an exception to be raised. Exception raised

When synchronizing banks and providers, if an account was already in your instance, it was synchronized too, using credits, and rasing an exception for 402: PAYMENT REQUIRED if the credits reach 0. Payment exception

After

Now if the xunnel_last_sync is not set, or has been set to False, it won't be added to the parameters causing the controlled exception to be raised. Exception catched

The method for sync the providers and accounts now use the same logic of the get_invoices-sat method of xunnel_invoice. Throwing an exception, and using its value in a custom wizard. Custom wizard

for the 402 server exception the journals (or accounts) are no longer refresh or from xunnel after sync (Only manual).

Edited by Javier Vega

Merge request reports