Payment or Billing Cycles stuck in a state of 'Generating' can occur for a few different reasons.
The most common reason is where the Generate_Payment_Cycles job (which polls every 5 minutes) is not enabled or installed. This can be the case particularly on test environments.
Where this job is enabled, there could also be errors that are blocking the generation of the cycle which will appear in our database tables and framework logs.
Another common check you can do is to look in the Locks Manager as there may be a lock from a previous attempt for the PAYMENT_CYCLES_GENERATING process that needs releasing back to be reused by the system again.
Payment Cycles won’t generate while importing e-invoices. These imports, especially from the Provider Portal, can take hours to process. The Payment Cycles will generate correctly once the import finishes.
We will be able to help you with this if this occurs, please raise a new case online and reference the title of this article. Please also include the following information:
Instance affected.
Cycle ID.
What time you roughly clicked to generate and how long you have been waiting.
For self hosted customers, along with the above provide the following to the case unless you are able to solve from this guided information:
Please check that your Generate Payment Cycle Job is enabled and running.
Please run: Select * from Error_Log Where Routine = 'generate_payment_cycles' Order By Time_Stamp desc
Please provide logs for the time window period between when the cycle was clicked to generate and 10-15 mins thereafter. Querying the payment_cycle table for the cycle ID (ID) can give you an exact timestamp for created_on to help you narrow the search.