This schedule holds a stored value django-ox cannot use. Its form and history are unavailable here. The details below explain your recovery options.
| Primary key | {{ schedule.pk|unlocalize }} |
|---|---|
| Name | {% if name is None %}Unreadable stored value{% else %}{{ name }}{% endif %} |
| Task key | {% if task_key is None %}Unreadable stored value{% else %}{{ task_key }}{% endif %} |
Stored values django-ox cannot use
-
{% for field, reason in problems %}
- {{ field }}: {{ reason }} {% endfor %}
To repair it, call
django_ox.stored.update_schedule(OxSchedule(pk={{ schedule.pk|unlocalize }}), {{ example }}){% if replaced %}
with replacement values for all these fields in the same call:
{{ replaced|join:", " }}{% else %} with a value for the example
argument; its current value also works{% endif %}.
{% if rewritten %}Any change made this way writes
{{ rewritten|join:", " }} afresh.{% endif %} A repaired schedule
starts from the moment of the repair. Ticks that came due while its
stored values could not be read are not fired afterwards. If you
cannot make this API call, send these instructions to a developer.
{% if stuck %}Only django_ox.stored writes these fields: {{ stuck|join:", " }}. Neither the API nor the admin can repair them. Use SQL to replace unreadable values or lower boundary_generation if it has reached its column's maximum. You can also delete the schedule and create it again.{% else %}The read could not identify the field, so this page cannot give repair instructions. Ask a developer to investigate the read error shown above.{% endif %} You can pause or delete the schedule, subject to permissions.
{% endif %}
To pause it, call
django_ox.stored.update_schedule(OxSchedule(pk={{ schedule.pk|unlocalize }}), enabled=False).
If the Disable button is available below, it does the same. Pausing does
not repair the stored values.